Riak can't use the vclock for conflict resolution on a fresh object,
i.e. one without a vclock. Deletes are writes. You should use get or
reload before writing to help Riak sequence your writes correctly.
On top of this, Riak has some weirdness around very quick sequences of
deletes/writes due, IIRC, to deletes not being tagged with a vector
clock. I... think... this will be addressed in an upcoming release.
--Kyle
On 06/03/2011 01:55 PM, Keith Bennett wrote:
Hi, all. I have a weird issue. I'm using the Riak ruby client. When I store
an object, create an object with the same bucket and key and delete it, then
create an object with the same bucket and key and store it again, it is not in
riak. Can someone tell me what I'm doing wrong? I posted my code here:
https://gist.github.com/1007142
Thanks very much,
Keith
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
