Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 23 Mar 2016 19:46:25 +0000 (UTC)
From: "Nick Bailey (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12712954.1399499047000.33327.1458762385594@Atlassian.JIRA>
In-Reply-To: <JIRA.12712954.1399499047000@Atlassian.JIRA>
References: <JIRA.12712954.1399499047000@Atlassian.JIRA>
 <JIRA.12712954.1399499047231@arcas>
Subject: [jira] [Commented] (CASSANDRA-7190) Add schema to snapshot manifest
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Nick Bailey commented on CASSANDRA-7190:
----------------------------------------

[~iamaleksey] I don't think CASSANDRA-9587 completely duplicates this. The schema we care about here is the latest schema at the time of the snapshot, not the schema associated with every sstable in the snapshot. The schema can change from sstable to sstable and the changes may be forward compatible but not backward compatible.

> Add schema to snapshot manifest
> -------------------------------
>
>                 Key: CASSANDRA-7190
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7190
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Jonathan Ellis
>            Priority: Minor
>
> followup from CASSANDRA-6326


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