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 <[email protected]> wrote: > > 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 <[email protected]> wrote: >> >> 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 getting [applied] false on the first write to >> cassandra. >> >> I have set retry policy as writeTimes = 0, so no retries are attempted. >> >> My application logs for reference: >> >> c-7967981443032352 - [INFO ] 2019-06-18T19:46:16.276Z [pool-15-thread-5] >> CreateService - SubPartition 104 >> c-7967981443032352 - [INFO ] 2019-06-18T19:46:16.805Z [pool-15-thread-5] >> Repository - Row[false, A, 1, 104] >> c-7967981443032352 - [INFO ] 2019-06-18T19:46:16.805Z [pool-15-thread-5] >> CreateService - SubPartition 104 CodeNumber 75191 DuplicateCodeGenerated A >> >> This is causing my count of writes to tables to differ from required 100000, >> to 100001, writing extra codes. >> >> Please guide here. >> >> -- >> Regards, >> Upasana Sharma > > > -- > Raman Gugnani > > 8588892293 > Principal Engineer > ixigo.com
