Hi,
*1. The below sequence of commands also does not appear to give an expected
output.*
Since, there is a delete command in the batch and then an LWT update using
IF EXISTS, in the final result row with id = 5 must get deleted.
cassandra@cqlsh> select * from demo.tweets;
*id* | *body*
One suggestion - I think Cassandra community is already having a drive to
update the documentation. This could be added to CQLSH documentation or
some other relevant documentation.
On Fri, May 3, 2019 at 12:56 AM Shaurya Gupta
wrote:
> Thanks Jeff.
>
> On Fri, May 3, 2019 at 12:38 AM Jeff Jirsa
Thanks Jeff.
On Fri, May 3, 2019 at 12:38 AM Jeff Jirsa wrote:
> No. Don’t mix LWT and normal writes.
>
> --
> Jeff Jirsa
>
>
> > On May 2, 2019, at 11:43 AM, Shaurya Gupta
> wrote:
> >
> > Hi,
> >
> > We are seeing really odd behaviour while try to delete a row which is
> simultaneously being
No. Don’t mix LWT and normal writes.
--
Jeff Jirsa
> On May 2, 2019, at 11:43 AM, Shaurya Gupta wrote:
>
> Hi,
>
> We are seeing really odd behaviour while try to delete a row which is
> simultaneously being updated in a light weight transaction.
> The delete command succeeds and the LWT u
Hi,
We are seeing really odd behaviour while try to delete a row which is
simultaneously being updated in a light weight transaction.
The delete command succeeds and the LWT update fails with timeout exception
but still the next select statement shows that the row still exists. This
occurs ones in
