Hi thanks, I was actually coming to the conclusion that to get this to work in my situation, I would need to embed a client side vector.
On Thu, Jun 20, 2013 at 5:34 PM, Jordan West <[email protected]> wrote: > Jeremy, > > What you are running into sounds a lot like the problems described in [1]. > > Jordan > > [1] https://github.com/ricardobcl/Dotted-Version-Vectors > > > On Tue, Jun 18, 2013 at 12:58 PM, Jeremy Ong <[email protected]>wrote: > >> >> >> >> On Tue, Jun 18, 2013 at 12:57 PM, Jeremy Ong <[email protected]>wrote: >> >>> Suppose I have two sources writing to the database, source A and source >>> B. >>> >>> Next, suppose A and B both issue a write to the database so they spawn >>> two siblings: [a1, b1]. >>> >>> Finally, suppose A writes another object using the metadata of the riak >>> object returned when writing a2. This will lead to the following situation: >>> >> Sorry typo. This should read: >> >> " >> Finally, suppose A writes another object using the metadata of the riak >> object returned when writing a1" >> >> >> >>> [a1, b1, a2]. >>> >>> Upon the next read, the client will be presented with these three >>> siblings. Is there a publicly exposed way to establish a strict ordering >>> between a1 and a2? >>> >>> Thanks, >>> Jeremy >>> >> >> >> _______________________________________________ >> riak-users mailing list >> [email protected] >> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >> >> >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
