[
https://issues.apache.org/jira/browse/COUCHDB-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682302#action_12682302
]
Robert Newson commented on COUCHDB-290:
---------------------------------------
for me (that is, couchdb-lucene) it would for verification and would save one
call per update. When I receive an update notification I GET /<dbname> to find
the latest update_seq, I then call _all_docs_by_seq with a startkey that I
track independently and a configurable limit that defaults to 1000. I loop
until I've processed up to the update_seq I got in the last call.
If the update_seq were provided in the notification, I could simplify the code.
I would think every update trigger must do something much the same, it seems
reasonable to add it the update notification.
If, as eric suggests, the before and after value was supplied, that might
further simplify the code.
> Include sequence number in update notifications
> -----------------------------------------------
>
> Key: COUCHDB-290
> URL: https://issues.apache.org/jira/browse/COUCHDB-290
> Project: CouchDB
> Issue Type: Improvement
> Affects Versions: 0.9
> Reporter: Elliot Murphy
> Priority: Minor
> Fix For: 0.9
>
> Attachments: couchdb-sequences.patch, couchdb-sequences.patch
>
>
> Hi! There's been requests to include the sequence number when sending an
> update notification. Thanks to the guidance from davisp on #couchdb on March
> 13th, I've been able to put together a little patch that does just that. In
> the future I'm interested in doing the same for the create notification, and
> perhaps extending create/delete/update notifications to include a list of
> affected doc IDs.
> For now though, just this simple patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
