[
https://issues.apache.org/jira/browse/COUCHDB-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175228#comment-13175228
]
Randall Leeds commented on COUCHDB-1367:
----------------------------------------
I suggested the heartbeat because we could make it look like last_seq, but we
don't even need to use heartbeat. We could emit a change that doesn't have a
corresponding id and revisions. Although, since the URL is /db/_revs_limit, we
could (to use that example) emit something like:
{"seq":X,"id":"_revs_limit","changes":[]}
I have no idea how badly that confuse existing clients, including CouchDB.
Putting it on the db info is the least obtrusive from an API standpoint. From a
code internals, I think everything would require some change (with the
exception of doing nothing about this). I'm going to step away for now, but if
you need any more color swatches I can send over some more samples.
> 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
