cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-9700) StreamSession selects canonical sstables, but uses the non-canonical instance
Date Wed, 01 Jul 2015 17:20:04 GMT
Benedict created CASSANDRA-9700:
-----------------------------------

             Summary: StreamSession selects canonical sstables, but uses the non-canonical
instance
                 Key: CASSANDRA-9700
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9700
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: Benedict
            Assignee: Benedict
             Fix For: 2.1.8


While implementing CASSANDRA-9699, I noticed that we are only checking that there _is_ a canonical
reader in StreamSession.getSSTablesForRanges, not that we are _using_ the canonical instance.
This means we are not using the full range of the sstable.

I'm not absolutely sure if this is a problem of correctness, as I'm not sufficiently versed
in how incremental repair works, but it looks worrisome to me.



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

Mime
View raw message