On Jun 16, 2011, at 5:53 PM, Andrew Thompson wrote:
> I've also
> added a 'deletedvclock' GET option to change the return behaviour for
> when a tombstone is found to instead return {deleted, VClock} so you can
> safely override a tombstone, instead of triggering a merge (or creating
> siblings).
On master ... Is this reflected in the REST API, so that e.g. when you get a
404 you may also get a VClock header if the object was previously deleted, but
Riak hasn't been able to effectuate that because a primary is down?
Kresten
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
