couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henrik Hofmeister (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1367) When settings revs_limit on db - the db increases its update_seq counter when viewing stats - but not when getting changes
Date Mon, 19 Dec 2011 14:15:30 GMT

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

Henrik Hofmeister commented on COUCHDB-1367:
--------------------------------------------

No im not - i just made a script ensuring it gets set on all dbs - to save a request i did
the "just set it to 1"  approach - assuming it wouldn't matter if i set it to 1 several times.
This is how i discovered there was such a problem. We had been getting it randomly before
- without ever realizing what the problem was exactly.

Its true that this specific case is for couchdb-lucene - however the general use case of being
able to predict how far you're away from being up to date is not couchdb-lucene specific -
i've for one created another in-house application that does exactly this - while performing
a chained map-reduce like operation (What im saying is - if you want to reap the benefits
of the changes feed and be aware of your progress - you'll need the right number)
                
> 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

        

Mime
View raw message