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-10572) SinglePartitionNamesCommand::canRemoveRow omits counter cells it shouldn't
Date Fri, 30 Oct 2015 15:47:27 GMT

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

Sylvain Lebresne commented on CASSANDRA-10572:
----------------------------------------------

bq. We can just short-circuit it for {{ClusteringIndexNamesFilter}} and {{queryNeitherCountersNorCollections()}}
in certain conditions.

I don't think I understand what your suggestion is (though I doubt I'll be a fan of a method
named {{queryNeitherCountersNorCollections}}).

> SinglePartitionNamesCommand::canRemoveRow omits counter cells it shouldn't
> --------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10572
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10572
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Aleksey Yeschenko
>            Assignee: Sylvain Lebresne
>             Fix For: 3.0.0
>
>
> Like with collections, we can never be sure we've exhausted all the sstables when reducing
the filter. The sstables can contain legacy local shards that need to be summed up. Unless
we look into the content of the cells (?), or until we get rid of the pre-2.1 values, we must
include all the sstables in the read (so long as clusterings overlap).
> This was not an issue with 2.1/2.2 as we've forced {{collectAllData}} always on that
path, but now we don't, and {{SinglePartitionNamesCommand}} should handle the case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message