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, which keeps growing with new insert for the same key. this issue happens when I insert via api using Phantom driver; works fine via cqlsh. not sure whether there is any limitation with "using timestamp" clause or a bug with Phantom driver. appreciate any advice/comments on Tuple or "using timestamp"...
