Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 16 Oct 2014 17:04:34 +0000 (UTC)
From: "Marcus Eriksson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12747680.1413192573000.279728.1413479074132@Atlassian.JIRA>
In-Reply-To: <JIRA.12747680.1413192573000@Atlassian.JIRA>
References: <JIRA.12747680.1413192573000@Atlassian.JIRA>
 <JIRA.12747680.1413192573483@arcas>
Subject: [jira] [Commented] (CASSANDRA-8110) Make streaming backwards
 compatible
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Marcus Eriksson commented on CASSANDRA-8110:
--------------------------------------------

We version the stream protocol separately, meaning we can have the same streaming protocol across different major versions. This ticket should make it possible to stream between different stream message versions whenever we add new stuff there (the thing that broke it between 2.1 and 3.0 was adding the SSTable level in the FileMessageHeader, CASSANDRA-7460 ).

> Make streaming backwards compatible
> -----------------------------------
>
>                 Key: CASSANDRA-8110
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8110
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Marcus Eriksson
>             Fix For: 3.0
>
>
> To be able to seamlessly upgrade clusters we need to make it possible to stream files between nodes with different StreamMessage.CURRENT_VERSION


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