[
https://issues.apache.org/jira/browse/COUCHDB-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928358#action_12928358
]
Sebastian Cohnen commented on COUCHDB-934:
------------------------------------------
The current architecture of couchdb's view system does process views in one
design document as a group. Therefore the view group fails if one view is
failing. That the view is rebuild is not duo to the fix, but duo to the fact,
that the view signature has changed. If you want to avoid this behavior, you
can use separate design documents for your views.
I have to admit that debugging a broken view can be a bit hard. There is
definitely room for improvement :)
> inside a design doc, a broken view makes all others views fail
> --------------------------------------------------------------
>
> Key: COUCHDB-934
> URL: https://issues.apache.org/jira/browse/COUCHDB-934
> Project: CouchDB
> Issue Type: Improvement
> Components: Database Core
> Affects Versions: 1.0.1
> Environment: All
> Reporter: Mickael Bailly
> Priority: Minor
>
> If a design document got a broken view, all other views don't work anymore.
> Steps to reproduce :
> 1/ create a new database
> 2/ Create a design doc :
> {
> "_id": "_design/doc1",
> "views": {
> "v1": {
> "map": "function() {}"
> },
> "v2": {
> "map": "thefunction() {}"
> }
> },
> "language": "javascript"
> }
> 3/ Create a doc :
> {
> "_id": "doc1"
> }
> 4/ Call the "v1" view
> It's annoying because :
> - we're unable to know what view fails to run
> - a fix on the broken view will result in the rebuilding of all other views
> of the design doc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
