cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11329) Indexers are not informed when expired rows are encountered in compaction
Date Tue, 05 Apr 2016 14:21:25 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226338#comment-15226338
] 

Sylvain Lebresne commented on CASSANDRA-11329:
----------------------------------------------

Sorry for the delayed review, +1.

Nit: there is a space missing in {{if (original !=null}} in {{SecondaryIndexManager.onPrimaryKeyLivenessInfo}}.

> 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)

Mime
View raw message