You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2018/03/26 09:56:59 UTC

[GitHub] ondra-novak opened a new issue #1235: Idea: Bring back all_or_nothing

ondra-novak opened a new issue #1235: Idea: Bring back all_or_nothing
URL: https://github.com/apache/couchdb/issues/1235
 
 
   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.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services