You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2016/01/14 13:10:39 UTC
[jira] [Commented] (CASSANDRA-11013) Stale entries not purged from
CompositesIndex
[ https://issues.apache.org/jira/browse/CASSANDRA-11013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098037#comment-15098037 ]
Benedict commented on CASSANDRA-11013:
--------------------------------------
+1
> Stale entries not purged from CompositesIndex
> ---------------------------------------------
>
> Key: CASSANDRA-11013
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11013
> Project: Cassandra
> Issue Type: Bug
> Components: Local Write-Read Paths
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Fix For: 3.0.x, 3.x
>
>
> Since CASSANDRA-9975, the cleanup of stale index entries at read time has been broken for {{CompositesIndex}} instances ({{KeysIndex}} is not affected).
> The issue is that the call to {{deleteAllEntries}} is made in the {{onClose}} method of the anonymous {{Transformation}}, where it should be in {{onPartitionClose}}. This wasn't caught by the existing unit test ({{o.a.c.db.SecondaryIndexTest::testDeleteOfInconsistentValuesInKeysIndex}} as it only checks that the stale entries are filtered from the returned results, not that they are actually purged from the index tables.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)