couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-223) Document a way to find out failed writes fro bulk requests and async writes
Date Thu, 19 Mar 2009 04:47:50 GMT

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

David Van Couvering commented on COUCHDB-223:
---------------------------------------------

That's odd.  In Apache Derby, anybody who went through a quick signup process could own issues,
even if they weren't contributors.

Anyway, I was looking at doing a first draft of this, but couldn't really figure out where
to put it in the Wiki.  Perhaps it could go into howto, but is there somewhere I'm missing
that already talks about bulk_docs functionality where I could just append/update the information?

Thanks!

> 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