You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2016/07/04 06:53:10 UTC
[jira] [Commented] (CASSANDRA-11944) sstablesInBounds might not
actually give all sstables within the bounds due to having start positions
moved in sstables
[ https://issues.apache.org/jira/browse/CASSANDRA-11944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360927#comment-15360927 ]
Marcus Eriksson commented on CASSANDRA-11944:
---------------------------------------------
ping on this [~benedict]
> sstablesInBounds might not actually give all sstables within the bounds due to having start positions moved in sstables
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-11944
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11944
> Project: Cassandra
> Issue Type: Bug
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Fix For: 3.0.x, 3.x
>
>
> Same problem as with CASSANDRA-11886 - if we try to fetch sstablesInBounds for CANONICAL_SSTABLES, we can miss some actually overlapping sstables. In 3.0+ we state which SSTableSet we want when calling the method.
> Looks like the only issue this could cause is that we include a few too many sstables in compactions that we think contain only droppable tombstones
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)