couchdb-dev mailing list archives

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

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

Robert Newson commented on COUCHDB-356:
---------------------------------------

I've measured the increased compaction overhead since the batch api change and, for my data
profile, it's not that big a deal (<12% reduction). The advantage of the new approach is
that the database is valid at each document insertion, which is a lovely thing to have, whereas
previously the entire batch would be effectively discarded if interrupted before reaching
the disk.

So, while the disk usage has increased over the previous batch api, it's only for, I think,
artificial cases with very small documents (and little or no attachments) that the overhead
might seem onerous, and in both of those cases compaction should be quick enough anyway.

> 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