incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "eric casteleijn (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-290) Include sequence number in update notifications
Date Thu, 02 Apr 2009 12:22:12 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694976#action_12694976
] 

eric casteleijn commented on COUCHDB-290:
-----------------------------------------

Now that 0.9 has landed, is there any chance this patch could land? I found an issue in our
specific use case which make it more that just optimization:

we log sequence numbers with timestamps to a file, and getting the sequence number from couch
with a request from the update trigger frequently returns a higher sequence number than one
would expect, since another update has already happened before the update trigger gets back
the sequence number. This can be coded around, but it makes it *very* hard to write deterministic
tests for the update triggers.

If there is anything I or Elliot can do to help this patch along, we'd be glad to do it.

> 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.10
>
>         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.


Mime
View raw message