Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <124765267.1245431287381.JavaMail.jira@brutus>
Date: Fri, 19 Jun 2009 10:08:07 -0700 (PDT)
From: "Chris Anderson (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Commented: (COUCHDB-218) Name view files by function
 signature for no-downtime deployments
In-Reply-To: <1042337539.1232552639584.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Anderson commented on COUCHDB-218:
----------------------------------------

as long as we're in there optimizing this stuff, we should make sure that the ddoc signature is generated the same regardless of the order of the views in the JSON document. this should be just a matter of sorting before taking the signature. it will prevent us from invalidating indexes that are actually valid.

> Name view files by function signature for no-downtime deployments
> -----------------------------------------------------------------
>
>                 Key: COUCHDB-218
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-218
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: JavaScript View Server
>            Reporter: Robert Newson
>            Assignee: Chris Anderson
>             Fix For: 0.10
>
>
> When a view is altered the .view file is deleted and then recreated. Any query (with update=false) in the interim gets no results even though the results from the old view would have been adequate.
> Consider switching the replacement view file in after it's been rebuilt like db compaction does.

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