[
https://issues.apache.org/jira/browse/COUCHDB-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682315#action_12682315
]
Robert Newson commented on COUCHDB-290:
---------------------------------------
@Jan I could, but I'm not going to. :) I'm not going to assume there's a time
when "no more new docs come in". Without some end condition, no new updates
will become searchable. Again, the reason I fetch the current update_seq is to
prevent a runaway while loop in my code, I could, instead, simply flush my
changes to the index every N minutes or N changes (whichever occurs first).
Since there's interest in that model anyway, I guess it's moot.
For now, I'm happy with the way I handle update notifications, receiving the
new update_seq in the notification would just be tidier for my case.
As Damien mentioned on the dev list, update notification might be obsolete soon
anyway, so we'll all need to change to a different solution anyway.
> 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.
