Thanks jens for quick reply, just a thought, cant sg-replicate update same local document instead of creating new document with reference to replication id. in worst case if sg-replicate restarts several times, there will be several local documents which are obsolete and these will not be purged in future.
On Wednesday, September 14, 2016 at 12:19:57 AM UTC+5:30, Jens Alfke wrote: > > > > On Sep 13, 2016, at 7:28 AM, arihant rk <[email protected] <javascript:>> > wrote: > > > > i have configured sg-replicate configuration in syncgateway > configuration and also provided replication id. but could able to see that > _sync:local documents. > > The replication algorithm creates these documents in the remote database > to store ‘checkpoint’ data. This helps to guard against inconsistencies if > the remote (or local) database regresses due to a restore from a backup. > Mobile clients create these too. > > Just ignore them. They’re an internal detail of Sync Gateway and the > replicator, just like everything else in the bucket that starts with > “_sync:”. > > —Jens -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/604bbee8-f3d9-44eb-a1e9-9c5b5b96498b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
