You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2015/08/06 17:06:05 UTC

[jira] [Commented] (CASSANDRA-9997) Removing cold_reads_to_omit in 2.2 is not backwards compatible with 2.1

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

Aleksey Yeschenko commented on CASSANDRA-9997:
----------------------------------------------

Marked as 2.2.1/Blocker temporarily, so that it doesn't slip. Will double-check if it really is, but we've promised the ability to migrate from 2.1 to 3.0 directly, and even 3.0 might have to support this.

> Removing cold_reads_to_omit in 2.2 is not backwards compatible with 2.1
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-9997
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9997
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Tommy Stendahl
>            Priority: Blocker
>             Fix For: 2.2.1
>
>
> Shouldn’t 2.2 be backwards compatible with 2.1? 
> The removal of the cold_reads_to_omit parameter in SizeTieredCompactionStrategy breaks backwards compatibility, wouldn't it be better to keep the same behaviour as in later 2.1 versions, the parameter is there but doesn’t do anything. The cold_reads_to_omit parameter should be removed in 3.0.
> This could be fixed by applying the patch in CASSANDRA-9203 on the 2.2 branch.



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