Asymmetric Sync

[sync-by-unito]

No description provided.

[in-jorgellose]

Is it still inprogress?

[nielsenko]

We have not begun working on it yet. Is this something you are missing?

[in-jorgellose]

Yes, we have a collection that's growing quite fast (it already has 90K docs), and we don't need that information on any device. Is there a way to prevent them from downloading it while this feature is not implemented? Like, for instance, setting the query in the sub to 1=2 so it never matches?

[nirinchev]

@in-jorgellose can you file a support ticket or ping your account executive with some info about your timelines (e.g. public testing/go-live dates) and they'll be able to either bump the priority of the feature or suggest workarounds.

[nielsenko]

@in-jorgellose Your suggested workaround will work.

You need a subscription, but if you make one that will never match anything, then any object you write will be transferred to the server, which will notice that the object is outside of you subscription cover and send a compensating write (here a delete) to remove it from the client.

This is obviously not the most efficient way, and proper support for asymmetric sync is much preferable (not to mention cheaper), but it will help you avoid the build up of objects on the client in the short term.

To be honest, asymmetric sync It is not our top priority currently, but as @nirinchev suggest there are ways to influence those 😉

[nielsenko]

@in-jorgellose We now have proper support as of v1.5.0

[in-jorgellose]

Thanks