From dev-return-19802-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Thu Dec 22 23:15:54 2011 Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0009D9D87 for ; Thu, 22 Dec 2011 23:15:53 +0000 (UTC) Received: (qmail 73169 invoked by uid 500); 22 Dec 2011 23:15:53 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 73113 invoked by uid 500); 22 Dec 2011 23:15:53 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 72977 invoked by uid 99); 22 Dec 2011 23:15:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Dec 2011 23:15:53 +0000 X-ASF-Spam-Status: No, hits=-2002.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Dec 2011 23:15:52 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id EECFB124D86 for ; Thu, 22 Dec 2011 23:15:30 +0000 (UTC) Date: Thu, 22 Dec 2011 23:15:30 +0000 (UTC) From: "Randall Leeds (Commented) (JIRA)" To: dev@couchdb.apache.org Message-ID: <1261779710.40879.1324595730979.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <2073127356.24602.1324243590757.JavaMail.tomcat@hel.zones.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 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COUCHDB-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175136#comment-13175136 ] Randall Leeds commented on COUCHDB-1367: ---------------------------------------- I'm confused about why a client listening to continuous _changes should care whether or not update_seq changes without emitting a document modification. I like to think that in the future other sorts of changes might be allowed to surface in that feed. Is there any place we guarantee that seq in the changes feed should be monotonic? I don't think so. It seems to me like this is not a problem. > 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