Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Adam FraserAdam FraserReporter
Adam FraserAdam FraserSprint
NonePriority
CriticalInstabug
Open Instabug
Details
Details
Assignee
Adam Fraser
Adam FraserReporter
Adam Fraser
Adam FraserSprint
None
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created April 26, 2017 at 5:24 PM
Updated May 25, 2017 at 5:53 PM
Resolved May 24, 2017 at 5:23 PM
When a document is deleted through Sync Gateway, we need to delete the document and update the mobile system xattr.
Currently we can't do this in a single operation - the subdoc MutateIn doesn't support document delete. When Sync Gateway does this in two operations (delete the doc, then update the xattr), there are two issues with a potential performance impact:
Delete processing itself (issuing two KV ops instead of one)
When Sync Gateway's initial delete comes back over the DCP feed, it looks like an SDK delete (the cas doesn't match the xattr cas), triggering Sync Gateway's import processing. This import processing will eventually no-op when it gets a cas error attempting to re-update the xattr, so it isn't a functional issue, but it would be preferable to avoid this processing overhead altogether.