Hi

Im creating a simple document and also updating it via iOS when the Sync 
Gateway is down. Upon restarting SG, the document (original and update 
revision) are both pushed to Couchbase server through Sync Gateway. But if 
I view the document properties, the _sync hash has "null" channels for both 
these revisions.

But if the SG is running and I make any updates to the same document, the 
channel is properly populated. Shouldnt the channel be updated even in the 
case the SG is brought up again and the documents are synchronized to the 
server.

This is causing me to skip revisions since Im doing a continuous feed on 
the _changes UI. If I just do a normal feed, I can see "holes" 
(corresponding to null channels) like
curl -N -X GET 
'http://localhost:4984/<DB>/_changes?style=all_docs&feed=normal'
returns
....
,{"seq":"public:21","id":"00E91C69-5296-4A69-A1AC-91FBF4BD3587","changes":[{"rev":"3-73a4481278d6441f1de493b22318e8cf"}]}
,{"seq":"public:24","id":"AA781585-FD0D-47BA-A70D-57114678A72B","changes":[{"rev":"2-c998bc58f846d7ebcb21df839df8fca3"}]}
,{"seq":"public:27","id":"54A6A32D-699E-4833-9DA0-8D9A46945E97","changes":[{"rev":"3-79cb0b2be14b28bca658defca9349513"}]}
,{"seq":"public:28","id":"9E18F7A0-CFC4-4ABD-A3F8-126433A90149","changes":[{"rev":"1-cc70d0d05ca64e8f3a1f08cd046a67cb"}]}

Sequences 22,23,25,26 are creates/updates I did when the Sync Gateway was 
down.

Im using the simple "public" channel as mentioned in the documentation for 
the GUEST user. Also, Im building sync gateway from source (Last week's 
changes) since I wanted to try out "bucket shadowing" (Im not using that 
feature but wanted to try out , which is why Im not using Beta2 build).

Thanks
Raja

-- 
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/310a46d7-6e25-4507-a825-faa36b7f471d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to