couchdb-dev mailing list archives

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

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

Chris Anderson commented on COUCHDB-356:
----------------------------------------

This is actually a bit outdated as we have a new batch infra based on Damien's parallel writers
patch.

Essentially we are always running batch=ok&wait=true now. Only we do the batching at the
file-write level, not in an in-memory data structure.

I think it's worth reevaluating the batch API for 0.11

> 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