t;dvv_enabled":true*
,"dw":"quorum",*"last_write_wins":false*
,"linkfun":{"mod":"riak_kv_wm_link_walker","fun":"mapreduce_linkfun"},
*"n_val":3*,"name":"*bucket-name*
","notfo
17, at 10:27, my hue <tranmyhue.grac...@gmail.com> wrote:
>
> > Dear Russell,
> >
> > Yes, I updated all registers in one go.
> > And I do not try yet with updating a single register at a time.
> > let me try to see. But I wonder that any affect on solving con
.br...@mac.com> wrote:
> So in you’re updating all those registers in one go? Out of interest, what
> happens if you update a single register at a time?
>
> On 7 Feb 2017, at 10:02, my hue <tranmyhue.grac...@gmail.com> wrote:
>
> > Dear Russel,
> >
> > > Can you
staurant_id">>,register},{register,<<>>,<<"
rest848e042b3a0488640981c8a6dc4a8281">>}},{{<<"restaurant_
status_id">>,register},{register,<<>>,<<"inactive">>}}
,{{<<"start_time">>,register},{re
rote:
> Originally I suspected the context which allows Riak to resolve conflicts
> was not present in your data, but I see it in your map structure. Thanks
> for supplying such a detailed description.
>
> How fast is your turnaround time between an update and a fetch? Even if
> the
Dear Riak Team,
I and my team used riak as database for my production with an cluster
including 5 nodes.
While production run, we meet an critical bug that is sometimes fail to
update document.
I and my colleagues performed debug and detected an issue with the scenario
as follow:
+ fetch
