Re: strange issue with Tuple in Cassandra 3.0

this is what I get from the trace log (repeated twice for each insert): INFO  [SharedPool-Worker-1] 2017-05-26 23:10:12,587  SLF4JAuditWriter.java:96 - host:/*.*.*.*|source:/*.*.*.*|user:*|timestamp:1495840212587|category:DML|type:CQL_UPDATE|ks:myks|cf:mytab|operation:INSERT INTO myks.mytab

Re: strange issue with Tuple in Cassandra 3.0

Can you upload the trace somewhere ? -- Jeff Jirsa > On May 27, 2017, at 5:34 PM, Subroto Barua > wrote: > > > i have a table with one of the column as Tuple datatype. > > when I insert rows with "using timestamp", I see multiple inserts in the > trace log

strange issue with Tuple in Cassandra 3.0

i have a table with one of the column as Tuple datatype. when I insert rows with "using timestamp", I see multiple inserts in the trace log and I see multiple data sets per partition key. for eg: for each partition key, I get extra tuple for each insert as opposed to 1 row for the key,