[GitHub] flimzy commented on a change in pull request #216: Re-write the bulk doc transaction description to reflect a single mode

[GitBox <gi...@apache.org>]

flimzy commented on a change in pull request #216: Re-write the bulk doc transaction description to reflect a single mode
URL: https://github.com/apache/couchdb-documentation/pull/216#discussion_r154307807
 
 

 ##########
 File path: src/api/database/bulk-api.rst
 ##########
 @@ -418,24 +418,16 @@ in bulk must be handled separately; see :ref:`api/db/bulk_docs/validation`.
 Bulk Documents Transaction Semantics
 ====================================
 
-CouchDB supports two different modes for updating (or inserting)
-documents using the bulk documentation system. Each mode affects both
-the state of the documents in the event of system failure, and the level
-of conflict checking performed on each document. The two modes are:
-
--  **non-atomic**
-
-   The default mode is `non-atomic`, that is, CouchDB will only guarantee
-   that some of the documents will be saved when you send the request.
-   The response will contain the list of documents successfully inserted
-   or updated during the process. In the event of a crash, some of the
-   documents may have been successfully saved, and some will have been
-   lost.
+Bulk document operations are **non-atomic**. This means that CouchDB does not
+guarantee that documents included in a bulk update (or insert), will be saved
 
 Review comment:
   I agree, that's a fair concern, and my original wording didn't make that point very well.
   
   I've updated the PR to include my last suggested wording.

----------------------------------------------------------------
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