Skip to content
This repository has been archived by the owner on Feb 5, 2024. It is now read-only.

Problem: Using all_or_nothing=true by default #119

Open
beberlei opened this issue Nov 11, 2015 · 1 comment
Open

Problem: Using all_or_nothing=true by default #119

beberlei opened this issue Nov 11, 2015 · 1 comment

Comments

@beberlei
Copy link
Member

We had several reports now that using the all or nothing strategy for documents leads to problems:

  • Creating conflict documents even though updates should be clean.
  • Performance drop in very large databases.

We should use the default CouchDB strategy all_or_nothing=false by default. This will be a huge BC break though.

@robsonvn
Copy link

robsonvn commented May 10, 2017

+1

I was receiving "HTTP Error with status 417 occurred while requesting /dbname/_bulk_docs. Error: not_implemented all_or_nothing is not supported" due to this using CouchDB 2.0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants