Jacek Lewandowski created CASSANDRA-19035:
---------------------------------------------
Summary: Consider adding a truncation record on table creation so
that we can avoid force recycle on table drop
Key: CASSANDRA-19035
URL: https://issues.apache.org/jira/browse/CASSANDRA-19035
Project: Cassandra
Issue Type: Improvement
Reporter: Jacek Lewandowski
By adding a truncation record with the same timestamp a table is created we
will have a marker that says all the data for that table prior to its creation
should be considered stale.
That should be more concise and more efficient approach than requiring recycle
of all the commit log segments, which starts with flushing all dirty tables.
The scenario in question is when a user recreates a table with the same ID and
there is data in the commit log for that table, we may experience data
resurrection in that new table.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
