[
https://issues.apache.org/jira/browse/CASSANDRA-11329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-11329:
----------------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.0.x)
(was: 3.x)
3.0.6
3.6
Status: Resolved (was: Ready to Commit)
Thanks, committed with nit fixed to 3.0 in
{{42459320586636c6dcbec9f56544d8a5256a3412}} and merged to trunk.
> Indexers are not informed when expired rows are encountered in compaction
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-11329
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11329
> Project: Cassandra
> Issue Type: Bug
> Components: Compaction
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Fix For: 3.6, 3.0.6
>
>
> When rows are merged during a compaction, if the row resulting from that
> merge is expired due to a row level ttl, registered indexes should be
> notified.
> Index implementers need to be aware that just because an expired row is
> written to the new SSTable, it doesn't necessarily mean that the index should
> purge its entry/entries for that row as there may still be be live data in
> other SSTables.
> That said, it should probably be the responsibility of the index
> implementation to manage that, but at the moment the handling of an
> {{onPrimaryKeyLivenessInfo}} event during compaction is a no-op and doesn't
> cause the registered indexes to be notified.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
