[jira] [Updated] (CASSANDRA-11944) sstablesInBounds might not actually give all sstables within the bounds due to having start positions moved in sstables

["Marcus Eriksson (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-11944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Eriksson updated CASSANDRA-11944:
----------------------------------------
    Assignee: Marcus Eriksson
      Status: Patch Available  (was: Open)

https://github.com/krummas/cassandra/commits/marcuse/intervaltreesstableset
http://cassci.datastax.com/view/Dev/view/krummas/job/krummas-marcuse-intervaltreesstableset-testall/
http://cassci.datastax.com/view/Dev/view/krummas/job/krummas-marcuse-intervaltreesstableset-dtest/

patch to remove the option to pick which SSTableSet you want returned, only LIVE sstables supported now. If you want canonical sstables within bounds you provide an IntervalTree built over those sstables.

Also includes CASSANDRA-11886 so that part might change depending on review in that ticket

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