mmcgrana / clj-riak Goto Github PK

Hi Mark,

Forgive me if I'm being dense, but it doesn't look like clj-riak supports specifying the vclock parameter when put'ing a value that overwrites a preexisting one. And I think this is required, but the Riak documentation might be outdated.

From the docs in the section on PUT:
http://wiki.basho.com/Basic-Riak-API-Operations.html

Some request headers are required for PUTs:

Content-Type must be set for the stored object. Set what you expect to receive back when >next requesting it.
X-Riak-Vclock if the object already exists, the vector clock attached to the object when read; >if the object is new, this header may be omitted

I noticed that if I rapidly (less than a ~2 second delay) put two different values into the same key, the first value wins and is not overwritten by the value that was written later. I should be able to use the :vclock arg (retrieved from a get before the second put) to ensure that the last item written wins.

I can write a patch to add :vclock to unparse-object, but wanted to make sure I wasn't misunderstanding the issue. Thanks for any input and happy new year!