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] Closed: (COUCHDB-223) Document a way to find out failed writes fro bulk requests and async writes
Date Sun, 22 Mar 2009 00:35:50 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Anderson closed COUCHDB-223.
----------------------------------

    Resolution: Fixed

David,

Thanks for documenting this. I think the appropriate place would be http://wiki.apache.org/couchdb/HTTP_Document_API
section "Modify Multiple Documents With a Single Request"

The only thing I'd add to your above discussion is to call the non-all_or_nothing behavior
the "default" so that people realize that they should expect that behavior.

If you don't feel like closing the loop on the wiki, please make a note here so someone else
can pick it up. I'm closing the ticket now because I think we have the relevant information
for documenting it, its just a matter of getting that info to the users.

Thanks!
Chris

> Document a way to find out failed writes fro bulk requests and async writes
> ---------------------------------------------------------------------------
>
>                 Key: COUCHDB-223
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-223
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Jan Lehnardt
>            Priority: Blocker
>             Fix For: 0.9
>
>
> A bulk docs request fails if one of the containing requests fail. In favour of multi-node
partitioning, this behaviour goes away and bulk writes will behave a lot like and async writes
and we should document the preferred way for clients to find failed writes.

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