> Is there any JIRA or enhancement to perhaps be able to detect when certain
> column tombstones can be deleted in minor compactions? The new introduction
> of SSTable min-max timestamps might help? or perhaps there are new ones
> coming up that I'm not aware of
https://issues.apache.org/jira
We've run exactly into the same problem recently. Some specific keys in a
couple CFs accumulate a fair amount of column churn over time.
Pre Cassandra 1.x we scheduled full compactions often to purge them.
However, when we moved to 1.x but we adopted the recommended practice of
avoiding full compa
Oke, thanks!
So a column tombstone will only be removed if all row fragments are
present in the tables being compacted.
I have a row called "Index" which contains columns like "page0",
"page1", "page2", etc. Every several minutes, new columns are created
and old ones deleted. The problem is that
> Does minor compaction delete expired column-tombstones when the row is
> also present in another table which is
No.
Compaction is per Column Family.
Tombstones will be expired by Minor Compaction if all fragments of the row are
contained in the SSTables being compacted.
Cheers
Hi all,
Does minor compaction delete expired column-tombstones when the row is
also present in another table which is not subject to the minor
compaction?
Example:
Say there are 5 SStables:
- Customers_0 (10 MB)
- Customers_1 (10 MB)
- Customers_2 (10 MB)
- Customers_3 (10 MB)
- Customers_4 (30
