-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CouchDB 3 Migration: Remove all_or_nothing flag #10780
Conversation
Can one of the admins verify this patch? |
test this please |
3 similar comments
test this please |
test this please |
test this please |
Jenkins results:
|
Thank you for providing this patch, Max. However, a deep investigation of the possible impacts with the removal of this |
test this please |
Jenkins results:
|
This has been superseeded by #11011, so I am closing this PR. |
Status
not-tested
Description
As part of the CouchDB Migration to 3.x ( #8853 ), the
all_or_nothing
flag has to be removed becauseit's no longer present (see apache/couchdb#1235 for a discussion).
Is it backward compatible (if not, which system it affects?)
NO
Related PRs
External dependencies / deployment changes
It depends on CouchDB 3.x