Thanks Brian, looking forward to the new client.
Thanks for the workaround too!
Cheers
Cos
On Friday, 27 February 2015 at 18:45, Brian Roach wrote:
> This was due to the UpdateValueFuture not checking for the exception
> when the get() methods were called. Just fixed this, it'll be in the
> ve
This was due to the UpdateValueFuture not checking for the exception
when the get() methods were called. Just fixed this, it'll be in the
very-soon-to-be-cut 2.0.1 release.
https://github.com/basho/riak-java-client/pull/503
Sync calls are just a wrapper around the async call that calls get() -
Yo
I have an edge case where consistency is favoured over availability so I’m
using a "consistent": true bucket type for a very specific operation.
I worked in testing my setup so ended up faking an entire failure by
deliberately using an incorrect vClock.
Using StoreValue, the (second) write fails
