Well, I'm not sure, and I'm new to Riak too, but I *think* you'd need to set allow_multi on the bucket.
-B. On Mon, Sep 23, 2013 at 4:01 AM, Gints <gints.gaili...@gmail.com> wrote: > I did a PUT, and the vclock that came back was: > a85hYGBgzGDKBVIcypz/fgZJFylnMCUy5rEyNOdtOc2XBQA= > > Then I read the object back, modified it, and PUT it again, providing the > old vclock, and got a new vclock: > a85hYGBgzGDKBVIcypz/fgZJFylnMCUy5bEyNOdtOc2XBQA= > > (Notice they are slightly different: Uy5rEy -> Uy5bEy) > > Then, I did a DELETE, using the first vector clock, not the second, updated > one. > > After that the object was gone, I could not find it in the database any > more. > > Is this supposed to be like that - deleting an object providing a stale > vclock actually deletes it? Or am I probably doing something wrong? > > Thanks, > Gints > > > > > -- > View this message in context: > http://riak-users.197444.n3.nabble.com/DELETE-and-vclocks-tp4029176.html > Sent from the Riak Users mailing list archive at Nabble.com. > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
