You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Robert Newson (JIRA)" <ji...@apache.org> on 2011/06/20 23:06:47 UTC
[jira] [Commented] (COUCHDB-1200) _update handler breaks after a
conflict is resolved
[ https://issues.apache.org/jira/browse/COUCHDB-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052220#comment-13052220 ]
Robert Newson commented on COUCHDB-1200:
----------------------------------------
Looks like it was fixed by this commit: 3a52f24172e62361e18f01691f034daf6851dbab
> _update handler breaks after a conflict is resolved
> ---------------------------------------------------
>
> Key: COUCHDB-1200
> URL: https://issues.apache.org/jira/browse/COUCHDB-1200
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core, Replication
> Affects Versions: 1.1
> Reporter: Pete Vander Giessen
> Fix For: 1.1.1
>
> Attachments: test_conflict_mine.sh
>
>
> My update handlers break after I've introduced and resolved a conflict. Despite the conflict being resolve, I get the following error when trying to run an update handler on a once-conflicted document:
> {"error":"conflict","reason":"Document update conflict."}
> The attached script reproduces the issue on 1.1.x. The issue does not appear when run against a build of trunk.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira