You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ryan Svihla (Jira)" <ji...@apache.org> on 2020/03/09 14:01:00 UTC
[jira] [Created] (CASSANDRA-15626) Need microsecond precision for
dropped columns so we can avoid timestamp issues
Ryan Svihla created CASSANDRA-15626:
---------------------------------------
Summary: Need microsecond precision for dropped columns so we can avoid timestamp issues
Key: CASSANDRA-15626
URL: https://issues.apache.org/jira/browse/CASSANDRA-15626
Project: Cassandra
Issue Type: Improvement
Components: Local/SSTable
Reporter: Ryan Svihla
In CASSANDRA-15557 the fix for the flaky test was reimplementing the logic from CASSANDRA-12997 which was removed as part of CASSANDRA-13426
However, since dropped columns are stored at a millisecond precision instead of a microsecond precision and ClientState.getTimestamp adds microseconds on each call we will lose the precision on save and some writes that should be dropped could reappear.
Note views affected as well
[https://github.com/apache/cassandra/blob/cb83fbff479bb90e9abeaade9e0f8843634c974d/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L712-L716]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org