rnewson commented on issue #1235: Idea: Bring back all_or_nothing URL: https://github.com/apache/couchdb/issues/1235#issuecomment-376157334 This would require a distributed transaction and is not something we anticipate bringing to CouchDB. Sent from my iPhone > On 26 Mar 2018, at 10:56, Ondrej Novak <notificati...@github.com> wrote: > > The conflict resolution is not atomic. Even if all conflicts are deleted along with updated document by a single _bulk_docs request, the data might be corrupted as result. There is a problem with validation function. If the validation fails for the updated document, conflicts are deleted, but main document is not updated. If the sender is unable to solve such situation immediately, the data from the conflicted documents are lost. > > Please bring back all_or_nothing, or a similar feature. It should just process validation for the all updated documents before they are processed normally. The implementation should be easy, the validation functions should be available on all nodes, so there is no barrier to validate these documents on any of that nodes. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub, or mute the thread. >
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
