[
https://issues.apache.org/jira/browse/COUCHDB-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski updated COUCHDB-902:
-----------------------------------
Fix Version/s: 1.1
1.0.2
Thanks, Klaus!
However, I'm a little uneasy making a change to a core module like that just
before a release. I'd prefer it if the change cooked in trunk for a little
while. That's why I'm proposing the following:
a) we commit Bob's change to couch_key_tree to trunk
b) we patch 1.0.x and 1.1.x at the HTTP layer by pruning the revision list
during an attachment update
We aren't in any danger of breaking something that isn't already broken, but we
still fix the user-facing issue of being unable recover attachments from a
conflict state. CouchDB 1.2 will have an improved Erlang API that never
returns a spurious 'conflict' result from a merge when the full revision lists
are used.
Anyone opposed? I'd like to release 1.0.2 ASAP after the HTTP fix is committed.
> Attachments that have recovered from conflict do not accept attachments.
> ------------------------------------------------------------------------
>
> Key: COUCHDB-902
> URL: https://issues.apache.org/jira/browse/COUCHDB-902
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Environment: trunk
> Reporter: Paul Joseph Davis
> Priority: Critical
> Fix For: 1.0.2, 1.1
>
> Attachments: 0001-Fix-COUCHDB-902.patch, couchdb-902-test-case.py
>
>
> Apparently if a document has been in a conflict, they will reject requests to
> add an attachment with a conflict error.
> I've tracked this down to couch_db_updater.erl line 501, but I'm not too
> familiar with this part of the code so I figured I'd fill out a ticket in
> case anyone else can go through this more quickly than me.
> Sure would be nice if I could attach a file when I create an issue...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
