Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Fri, 28 Jun 2013 01:36:20 +0000 (UTC)
From: "Alexander Shorin (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12480908.1290688389905.182514.1372383380570@arcas>
In-Reply-To: <JIRA.12480908.1290688389905@arcas>
References: <JIRA.12480908.1290688389905@arcas>
Subject: [jira] [Updated] (COUCHDB-965) Notify client when querying a badly
 generated view
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alexander Shorin updated COUCHDB-965:
-------------------------------------

    Component/s: View Server Support
    
> Notify client when querying a badly generated view
> --------------------------------------------------
>
>                 Key: COUCHDB-965
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-965
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: View Server Support
>            Reporter: afters
>            Priority: Minor
>
> Currently, the only notification on an exception thrown during view-generation is in the log. Bugs that cause such exceptions are often hard to hunt down as the client may have no indication that a bug has occurred, and no incentive to sniff around couchdb's log. Automatic testing for such bugs is also difficult.
> I suggest having some kind of strict/fragile mode (either per couch, or per db), that would make sure that an error is returned when querying such badly generated views.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira