On Wed, Apr 29, 2015 at 5:13 PM Jens Alfke <j...@couchbase.com> wrote:
> > Does the document have a lot of (resolved or unresolved) conflicts? SG’s > current rev-pruning algorithm has the problem that it won’t prune revisions > that are recent ancestors of any leaf revision, even a deletion tombstone. > That means that if you have a document with a zillion revisions, but > there’s a conflict branch at least every *revs_limit* generations, > nothing ever gets pruned. > So my question - is there a way I can reconcile conflicts in the sync gateway via API? I did a quick search of the python api lib and didn't see anything related to conflicts. If this can only be done on device, that's a bit of plumbing that concerns me. I'd rather be able to handle these on the server for my users. For me, conflict resolution is quite simple. I just take the one with the latest timestamp and that will suffice. > We just fixed this for SG 1.1, and we have confirmation from a customer > that it fixed an issue like yours. You could try building your own SG from > the ‘release/1.1.0’ branch and see if it helps you. Or wait a week or two* > for the 1.1 developer preview release. > This branch definitely helped! I'm running it right now and syncs that were taking 15+ mins are now down to about 90 seconds or less. Thanks!! -j -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to mobile-couchbase+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/CAN8S9iJamnfZBiGCqz90veLnfzKWeeZb9OLZC_h%2BVAZ9aP7sBw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
