CouchDB
  1. CouchDB
  2. COUCHDB-1367

update_seq does not always reflect the seq of the latest document update

    Details

    • Type: Bug Bug
    • Status: Reopened
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.1.1
    • Fix Version/s: None
    • Component/s: HTTP Interface
    • Labels:
    • Environment:

      Any

      Description

      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.

        Activity

        Henrik Hofmeister created issue -
        Bob Dionne made changes -
        Field Original Value New Value
        Assignee Bob Dionne [ dionne ]
        Randall Leeds made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Assignee Bob Dionne [ dionne ]
        Resolution Not A Problem [ 8 ]
        Randall Leeds made changes -
        Resolution Not A Problem [ 8 ]
        Status Closed [ 6 ] Reopened [ 4 ]
        Randall Leeds made changes -
        Summary When settings revs_limit on db - the db increases its update_seq counter when viewing stats - but not when getting changes update_seq does not always reflect the seq of the latest document update
        Description 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.
        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.
        Robert Newson made changes -
        Status Reopened [ 4 ] Resolved [ 5 ]
        Fix Version/s 1.2 [ 12315198 ]
        Fix Version/s 1.3 [ 12318350 ]
        Fix Version/s 1.1.2 [ 12318873 ]
        Resolution Fixed [ 1 ]
        Robert Newson made changes -
        Fix Version/s 1.2 [ 12315198 ]
        Fix Version/s 1.3 [ 12318350 ]
        Fix Version/s 1.1.2 [ 12318873 ]
        Robert Newson made changes -
        Comment [ Added a clause for empty list for builtin_stats which fixes the function_clause. ]
        Robert Newson made changes -
        Resolution Fixed [ 1 ]
        Status Resolved [ 5 ] Reopened [ 4 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Henrik Hofmeister
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development