[
https://issues.apache.org/jira/browse/COUCHDB-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181968#comment-13181968
]
Robert Newson commented on COUCHDB-1367:
----------------------------------------
FYI: I've fixed couchdb-lucene. Instead of using "update_seq" from GET /dbname
I instead grab "last_seq" from GET /dbname/_changes?limit=0&descending=true.
> update_seq does not always reflect the seq of the latest document update
> ------------------------------------------------------------------------
>
> Key: COUCHDB-1367
> URL: https://issues.apache.org/jira/browse/COUCHDB-1367
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Affects Versions: 1.1.1
> Environment: Any
> Reporter: Henrik Hofmeister
> Priority: Minor
> Labels: revs_limit
>
> Certain operations, (currently _revs_limit and _security changes) cause the
> database header's update_seq to increase when the by_seq index (and therefore
> _changes) has not changed, which is confusing in light of the naming
> consistency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
