You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Yuki Morishita (JIRA)" <ji...@apache.org> on 2015/07/02 18:55:04 UTC

[jira] [Commented] (CASSANDRA-9700) StreamSession selects canonical sstables, but uses the non-canonical instance

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

Yuki Morishita commented on CASSANDRA-9700:
-------------------------------------------

+1

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