You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (JIRA)" <ji...@apache.org> on 2016/03/09 20:02:40 UTC

[jira] [Created] (CASSANDRA-11329) Indexers are not informed when expired rows are encountered in compaction

Sam Tunnicliffe created CASSANDRA-11329:
-------------------------------------------

             Summary: 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.0.x, 3.x


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)