If applied is false it’s not the first write, the value already exists. You’ve
likely got a concurrency issue app side or you don’t understand the concurrent
queries you’re issuing to the db
> On Jul 8, 2019, at 10:08 PM, raman gugnani wrote:
>
> Hi Team,
>
> Can anyone help on the same.
>
Hi Team,
Can anyone help on the same.
Cassnadra driver says write is not done but eventually write has been done.
On Mon, 8 Jul 2019 at 12:31, Upasana Sharma <028upasana...@gmail.com> wrote:
>
> Hi,
>
> I am using an LWT Insert transaction similar to:
>
> INSERT INTO table1 (code, id, subpart)
Hi,
This https://www.datastax.com/dev/blog/row-level-isolation link mentions:
"
For atomicity, the guarantee actually extends *across column families
(within the same keyspace): updates for the same partition key are
persisted atomically even for different column families*. This is not the
case ho
Hi,
I am using an LWT Insert transaction similar to:
INSERT INTO table1 (code, id, subpart) VALUES (:code, :id, :subpart) IF NOT
EXISTS
With
readConsistency="LOCAL_SERIAL"
writeConsistency="LOCAL_QUORUM"
Cassandra Driver: 3.6.0
Cassandra Version: Cassandra 3.11.2
The problem is that I am gett
