I believe you are referring to the 'all_or_nothing' option. This was dropped in CouchDB 2.0 (and in IBM Cloudant as well): http://docs.couchdb.org/en/latest/whatsnew/2.0.html#upgrade-notes
Cheers, Kyle On Thu, Mar 15, 2018 at 6:07 PM, Sasha Fonseca <sasha...@gmail.com> wrote: > Hello, > > I've began using and experimenting with CouchDB and I was looking into > doing bulk insert of documents. I'd like to do them in a transactional > fashion (insert all of them or rollback and don't insert any). The HTTP API > Reference talks about two modes: > > CouchDB supports two different modes for updating (or inserting) documents > > using the bulk documentation system. Each mode affects both the state of > > the documents in the event of system failure, and the level of conflict > > checking performed on each document. The two modes are: > > > *non-atomic* > > > > The default mode is non-atomic, that is, CouchDB will only guarantee that > > some of the documents will be saved when you send the request. The > response > > will contain the list of documents successfully inserted or updated > during > > the process. In the event of a crash, some of the documents may have been > > successfully saved, and some will have been lost. > > > > However, there's no reference about the other mode? Using the search bar in > the doc returns no results about an atomic mode and it doesn't seem clear > how to use either of these modes for bulk inserts. > > Any help on this would be appreciated. > > Thanks >
