> Can you outline the detailed steps to reproduce the issue Yuji ?
>
Our application requests UPDATE a row.
The row has "id"(PRIMARY KEY), "revision" and "value" columns.
The updating condition is EQ of current "revision".
When the problem happens, the following sequence is executed in one thread
Can you outline the detailed steps to reproduce the issue Yuji ?
On Mon, Jul 25, 2016 at 3:16 AM, Yuji Ito wrote:
> thanks, Ryan
>
>
>> are you using one of the SERIAL Consistency Levels?
>
> yes, I use read with ConsistencyLevel.SERIAL.
>
> On Mon, Jul 25, 2016 at 10:10 AM, Ryan Svihla wrote:
thanks, Ryan
> are you using one of the SERIAL Consistency Levels?
yes, I use read with ConsistencyLevel.SERIAL.
On Mon, Jul 25, 2016 at 10:10 AM, Ryan Svihla wrote:
> are you using one of the SERIAL Consistency Levels?
>
> --
> Ryan Svihla
>
> On July 24, 2016 at 8:08:01 PM, Yuji Ito (y...@
are you using one of the SERIAL Consistency Levels?
--
Ryan Svihla
On July 24, 2016 at 8:08:01 PM, Yuji Ito (y...@imagine-orb.com) wrote:
> Hi,
>
> I have another question about CAS operation.
>
> Can a read get stale data after failure in commit phase?
>
> According to the following article,
>
Hi,
I have another question about CAS operation.
Can a read get stale data after failure in commit phase?
According to the following article,
when a write fails in commit phase (a WriteTimeout with WriteType SIMPLE
happens),
a subsequent read will repair the uncommitted state
and get the latest
