On Mon, Jan 20, 2014 at 12:50 PM, Russell Brown wrote:
>
> I guess you must be right. Riak’s vnode version vectors, in the case
> described in 3.2 would generate siblings. The put of `v` with an empty VV
> would lead to the value `v` and VV {b, 1}, but the put of `w` with no VV
> would not lead to
On 20 Jan 2014, at 20:35, Elias Levy wrote:
> On Mon, Jan 20, 2014 at 12:14 PM, Russell Brown wrote:
> Longer answer: Riak gave users the option of client or _vnode_ ids in version
> vectors. By default Riak uses vnode ids. Riak erred on the side of caution,
> and would create false concurren
On Jan 20, 2014, at 12:35 PM, Elias Levy wrote:
> On Mon, Jan 20, 2014 at 12:14 PM, Russell Brown wrote:
> Longer answer: Riak gave users the option of client or _vnode_ ids in version
> vectors. By default Riak uses vnode ids. Riak erred on the side of caution,
> and would create false concu
On Mon, Jan 20, 2014 at 12:14 PM, Russell Brown wrote:
> Longer answer: Riak gave users the option of client or _vnode_ ids in
> version vectors. By default Riak uses vnode ids. Riak erred on the side of
> caution, and would create false concurrency, rather than lose writes.
>
I am curious as to
Hi Elias,
Answers inline below:
On 20 Jan 2014, at 19:31, Elias Levy wrote:
>
> On Sun, Jan 19, 2014 at 9:00 AM, wrote:
> From: Luc Perkins
> * Reduced sibling creation, inspired by the dotted versions vectors research
> from Preguiça, Baquero, et al[1]
>
> [1] http://arxiv.org/abs/1011.58
On Sun, Jan 19, 2014 at 9:00 AM, wrote:
> From: Luc Perkins
> * Reduced sibling creation, inspired by the dotted versions vectors
> research from Preguiça, Baquero, et al[1]
>
> [1] http://arxiv.org/abs/1011.5808
>
A quick skim over the paper seems to indicate that version vectors with
per-serv
