This sure looks like a bug...?
btilly at gmail.com
Mon Apr 18 20:12:44 EDT 2011
On Mon, Apr 18, 2011 at 4:59 PM, Dan Reverri <dan at basho.com> wrote:
> Hi Bryan,
> This is an excellent question and one of the more difficult areas of Riak to
> understand. The source of confusion in this situation is vector clocks. Riak
> maintains a vector clock for every object which is used to track different
> versions of the object and potentially auto-repair out-of-sync data.
> I recommend reviewing this page in the wiki:
I actually had a question about that page. Why is it that when there
is a conflict we can only get the conflicting versions of the data?
If I'm going to try to resolve the conflict intelligently, I really
want the common ancestor as well so that I can try to do a 3-way
More information about the riak-users