Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <32903392.428151282161499515.JavaMail.jira@thor>
Date: Wed, 18 Aug 2010 15:58:19 -0400 (EDT)
From: "Klaus Trainer (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Updated: (COUCHDB-858) GET /db/_design/doc/_info should not
 trigger an update
In-Reply-To: <7647854.425941282157836376.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/COUCHDB-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Klaus Trainer updated COUCHDB-858:
----------------------------------

    Attachment: 0001-Don-t-trigger-a-view-update-when-sending-a-GET.patch

Here the relevant piece from the IRC log:

kocolosk: i believe all one needs to do is remove the spawn_link couch_view_updater:update line from couch_view_group:init

I just wanted to see if kocolosk was right, and yes he was :)

The attached patch makes sure that a GET request to /db/_design/doc/_info never triggers an update of the view group.

> GET /db/_design/doc/_info should not trigger an update
> ------------------------------------------------------
>
>                 Key: COUCHDB-858
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-858
>             Project: CouchDB
>          Issue Type: Bug
>         Environment: All
>            Reporter: mikeal
>         Attachments: 0001-Don-t-trigger-a-view-update-when-sending-a-GET.patch
>
>
> Ran across this in my futon rewrite.
> A call to the info for a ddoc triggers an update in some cases. koco says it's when that "group is open". 
> This request needs to either not trigger an update or respect stale=ok.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.