[couchdb-documentation] 01/03: group fixed quorum operations

[ja...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jan pushed a commit to branch 2.2.0-release-notes-2
in repository https://gitbox.apache.org/repos/asf/couchdb-documentation.git

commit 473b638c6e98619717f499080b30bf07227fd73e
Author: Jan Lehnardt <ja...@apache.org>
AuthorDate: Tue Jul 24 12:13:46 2018 +0200

    group fixed quorum operations
    
    @wohali: I know you are going for e=sequential issue ids, but this
    one felt weird when reading through. Since the only substantial
    difference is create/delete, coming up on delete, one reads this
    as a duplicate.
    
    I hope you agree with the out-of-order-exception for this one.
---
 src/whatsnew/2.2.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/whatsnew/2.2.rst b/src/whatsnew/2.2.rst
index cfa1918..318bd10 100644
--- a/src/whatsnew/2.2.rst
+++ b/src/whatsnew/2.2.rst
@@ -108,6 +108,10 @@ Features
   now return a ``202 Accepted`` code if possible, indicating that at least one node
   has written the database record to disk, and that other nodes will be updated as they
   return to an online state. This replaces the former ``500`` internal error.
+* :ghissue:`1136`, :ghissue:`1139`: When deleting a database in a cluster without
+  quorum, CouchDB will no longer throw a ``500`` error status, but a ``202`` as long as
+  at least one node records the deletion, or a ``200`` when all nodes respond. This fix
+  parallels the one made for :ghissue:`603`.
 * :ghissue:`745`: CouchDB no longer fails to complete replicating databases with
   large attachments. The fix for this issue included several related changes:
 
@@ -153,10 +157,6 @@ Features
   in a database by adding ``conflicts: true`` to a mango selector.
 * :ghissue:`1126`: When queried back after saving, replication documents no longer
   contain sensitive credential information (such as basic authenticataion headers).
-* :ghissue:`1136`, :ghissue:`1139`: When deleting a database in a cluster without
-  quorum, CouchDB will no longer throw a ``500`` error status, but a ``202`` as long as
-  at least one node records the deletion, or a ``200`` when all nodes respond. This fix
-  parallels the one made for :ghissue:`603`.
 * :ghissue:`1203`: The compaction daemon now has a snooze period, during which it waits
   to start the next compaction after finishing the previous one. This value is useful
   in ``couch_peruser`` setups, which can cause a CPU spike every ``check_interval``