Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Tue, 13 Dec 2011 01:09:30 +0000 (UTC)
From: "Randall Leeds (Closed) (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: 
 <1925322548.3783.1323738570563.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (COUCHDB-282) Abort views that have exceptions in
 the view server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Randall Leeds closed COUCHDB-282.
---------------------------------

    Resolution: Won't Fix

I'm closing this as "Won't Fix" because, while it's possible to catch syntax errors when compiling the view functions, it's not easy to know whether a syntax error may have been thrown by a user calling "eval" or something else tricky.

In other words, it's hard to disambiguate between errors caused by the view code and errors caused by the input data.

Also, this hasn't been updated in a long time.
                
> Abort views that have exceptions in the view server
> ---------------------------------------------------
>
>                 Key: COUCHDB-282
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-282
>             Project: CouchDB
>          Issue Type: Bug
>          Components: JavaScript View Server
>    Affects Versions: 0.8, 0.8.1
>         Environment: All
>            Reporter: kowsik
>
> I'm incrementally experimenting with new views on a 100K document db. If there's a typo in the javascript view or some other exception, there's a spew of logs in couch.log while each of the couch documents continue to go through the map/reduce code (which is buggy). This takes about 15 minutes before I can update the view and re-query again. It would be awesome if couch can handle exceptions in the view server and stop processing so that the fix can be made.

--
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