[
https://issues.apache.org/jira/browse/COUCHDB-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173289#comment-13173289
]
Henrik Hofmeister commented on COUCHDB-1367:
--------------------------------------------
What i'm puzzled about - is what would i ever need the update_seq for ? It
allows me to - see that there has been made a change - however in the changes
view it shows me that there are no changes? Only in the cases where it differs
for last_seq of course - but what could i ever possibly use that number for?
That is - a number - signalling that i have either updated revs_limit or a
random other number of internal api calls ? Its absolutly useless - especially
while i have no way of getting to know whats changed.
update_seq would - in any possible case - be expected by the user to reflect
your core feature - the changes feed?
Not making it into a huge problem - but the only real fix for a production env.
product like couchdb is to not add to the confusion - but fix the confusion
(like not adding another number to the db info page) . That would give you 2
numbers - one that is useless (update_seq) and one that is the one you'd expect
(last_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
