Alexander Shorin created COUCHDB-2352:
-----------------------------------------

             Summary: Drop X-Couch-Full-Commit header and batch=ok query 
parameter
                 Key: COUCHDB-2352
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2352
             Project: CouchDB
          Issue Type: Improvement
      Security Level: public (Regular issues)
          Components: Database Core
            Reporter: Alexander Shorin


Following discussion on IRC.

CouchDB uses both header and query parameter to override default commit policy. 
For instance, the replicator stores all the changes with using 
"X-Couch-Full-Commit: false" header to temporary enable "delay_commit" option 
in case if it not and later sends a request against `/_ensure_full_commit` 
endpoint to flush all the changes on disk.

Since CouchDB 2.0 delayed commits are disabled by default and was always not 
recommended to keep it enabled in production unless you're need in nicer 
benchmark numbers. Using commit policy override hacks, especially by the so 
core tool as replicator may not be wise and lead to bugs, especially for 
cluster mode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to