There are certainly cases where corruption has happened in cassandra (rare,
thankfully), but like I mentioned, I'm not aware of any that only corrupted
timestamps. It wouldn't surprise me to see a really broken clock, and it
wouldnt' surprise me to see bit flips on bad hardware (even hardware with
Thanks for your help, I wrote a script to cycle through these early records and
try to update them (some columns were missing, but could be gleaned from
another db), then do the update, re-read, and if its not correct figure out the
write time and re-issue the update with a timestamp + 1. We’re
It's a long, so you can't grab it with readInt - 8 bytes instead of 4
You can delete it by issuing a delete with an explicit time stamp at least 1
higher the. The timestamp on the cell
DELETE FROM table USING TIMESTAMP=? WHERE
https://cassandra.apache.org/doc/latest/cql/dml.html#delete
T
Hello,
We have a Cassandra database that is about 5 years old and has gone through
multiple upgrades. Today I noticed a very odd thing (current timestamp would
be around 1502957436214912):
cqlsh:siq_prod> select id,account_id,sweep_id from items where id=34681132;
id | account_i
