couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-356) batch=ok should take a wait=true option
Date Mon, 21 Dec 2009 16:46:18 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793258#action_12793258
] 

Paul Joseph Davis commented on COUCHDB-356:
-------------------------------------------

FWIW, Robert Newson pointed out that the batch writer API doesn't minimize writes like the
batch api did which ends up resulting in larger database files due to more writes. Plus unless
I'm mistaken the new write merging won't speed up the single client case, just when multiple
writers are writing simultaneously.

Bottom line, I could see a case for bringing the batch API back.

> batch=ok should take a wait=true option
> ---------------------------------------
>
>                 Key: COUCHDB-356
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-356
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>            Reporter: Chris Anderson
>             Fix For: 0.11
>
>
> This would hold the connection to the client until the document has been committed, instead
of returning immediately with a 202 Accepted

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message