On Tue, Nov 6, 2012 at 9:57 PM, Elias Levy wrote:
> It's also not clear from the docs what Riak considers the latest value
> to return if allow_mult is false and so is last_write_wins, when you
> have a conflict.
>
Any Basho folks have an answer to this one? How does Riak resolve a
conflict on a
Elias,
The resulting strategy of allow_mult=false and last_write_wins=false
(which is a simplification for developer-friendliness mostly):
1) Resolve differences using the vector clock first.
2) If siblings still exist, return the one with the latest timestamp.
So in a sense, it's a combination
Sean,
Thanks for the explanation.
One last follow up. During testing I noticed that when using
if_not_modified against a test cluster with a node using the PB interface
and the Ruby client, if the bucket had an n_val greater than the number of
nodes, the put would fail with 'modified' error, even
G'day!
Just to add to the list of people asking questions about migrating to
1.2.1 . . .
We're about to migrate our 4 node production Riak database from 1.1.1 to
1.2.1. At the same time we're also migrating from virtual machines to
physical machines. These machines will have new names and IP
I finally got the processes to start on machine reboot. I just have one
final question. When I execute 'riak-admin status' I get an error 'Node is
not running!'. But, when I execute 'sudo riak-admin status' I get the status
that I expect. Why in order to get the status do I need to be root? Also
I've been looking at switching my Ruby interactions with Riak to Ripple and was
trying to figure out how conflict resolution works. I saw one post saying it
was targeted for 1.0 and some code for it in the master branch on github, but
not documentation. Is there some that I've missed I could r
