> That would break too much Can you please give any example of stuff that could be broken by this kind of tail?
> we can add metadata wherever seems most natural Add into documents or as a tail? As for me, this metadata isn‘t about documents, it‘s about state of a cluster during particular request. ermouth 2015-10-13 12:23 GMT+03:00 Robert Samuel Newson <[email protected]>: > That would break too much. > > One way out of this is to exclude this information by default and add it > only when requested with a request parameter With that, we can add metadata > wherever seems most natural. Clients that ask for the information are > required to understand it. Similar to ?conflicts=true. > > B. > > > On 13 Oct 2015, at 01:51, ermouth <[email protected]> wrote: > > > > Shouldn‘t it be a header if single doc requested, and smth like {ok:true, > > rows:[row1, row2 ... rowN], sloppy_quorum:[id1, id2 ... idN]} for > _all_docs > > request? > > > > ermouth > >
