On 11/02/2011 10:40 AM, Justin Karneges wrote:
Thanks everyone for these replies (and also Aphyr, off-list). It has helped me
confirm my suspicions and sounds like I'm on the right track.
For one of my keys, I am doing sort of a manual "last write wins" by having
the reader sort siblings by tim
_
> > Fra: riak-users-boun...@lists.basho.com [
>
> riak-users-boun...@lists.basho.com] På vegne af Justin Karneges [
> jus...@affinix.com]
>
> > Sendt: 1. november 2011 21:34
> > Til: riak-users@lists.basho.com
> > Emne: safely
ield the same - i.e., f(X,X) =
X.
>
> Fra: riak-users-boun...@lists.basho.com [
riak-users-boun...@lists.basho.com] På vegne af Justin Karneges [
jus...@affinix.com]
> Sendt: 1. november 2011 21:34
> Til: riak-users@lists.basho.com
> Emne: safely
f(X,X) = X.
Fra: riak-users-boun...@lists.basho.com [riak-users-boun...@lists.basho.com]
På vegne af Justin Karneges [jus...@affinix.com]
Sendt: 1. november 2011 21:34
Til: riak-users@lists.basho.com
Emne: safely resolving conflicts on read
Hi,
http://wiki.basho.
Hi,
http://wiki.basho.com/Vector-Clocks.html contains this text:
"It should be noted that if you are trying to resolve conflicts automatically,
you can end up in a condition with which two clients are simultaneously
resolving and creating new conflicts."
If conflict resolution is moved to the
