[
https://issues.apache.org/jira/browse/COUCHDB-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173086#comment-13173086
]
Bob Dionne commented on COUCHDB-1367:
-------------------------------------
I'm a little confused then. It seems if c-l has access to the last_seq then it
should be able to determine if there are no changes of interest. I thought the
commentary on IRC was that this was not the case because it uses the continuous
feed.
Adding last_seq to the db info request will certainly solve it, though look a
little redundant to the user as it will be almost always be equal to update_seq
> When settings revs_limit on db - the db increases its update_seq counter when
> viewing stats - but not when getting changes
> --------------------------------------------------------------------------------------------------------------------------
>
> 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
> Assignee: Bob Dionne
> Priority: Minor
> Labels: revs_limit
>
> If you put a number to _revs_limit on a db (to update it) - the
> http://host/dbname/ info document gets an increase in update_seq number -
> however the changes feed does not contain this change (while its not a
> change). This causes the update_seq in the dbinfo doc and the last seq in the
> changes feed to differ - which breaks any application depending on the
> update_seq number as the expected sequence size of the db (in my case -
> couchdb-lucene that will only respond to stale requests because it thinks its
> not up to date)
> I know this is an edge case - but still its something fairly fundamental -
> that clearly is not working as intended.
--
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
