Clarifying "Read-before-Write"

So I was just reading and thinking about this, and I don't understand the advice offered under "Read-before-Write" at http://wiki.basho.com/Client-Implementation-Guide.html. "Riak will return an encoded vector clock > with every "fetch" or "read" request

Re: Faster deletes?

I think that writes to Riak will always be faster than other operations. It has to do with the fact that writes are append only, whereas deletes, for example, must write a tombstone into all of the replicas. I'm basically paraphrasing this message since I don't understand how this works 100%: htt

Re: Faster deletes?

I'm still interested in this problem (deletes lagging way behind inserts). Is there anything about the technology of Riak itself that might explain this, or is it instead something to do with the map/reduce phase in order to find keys to delete? Andy indicated that the map part of what he was d

RJC 1.0.2 released

Hi, I just pushed the release button for riak-java-client 1.0.2. It is on oss.sonatype and will find its way to maven when they sync. It is just a small bug fix release. Bugs fixed are: Incoming post commit hooks added to the pre-commit list (thanks to Bob Baker from Sharecare for that fix!)[1