Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 13 Apr 2016 17:36:25 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12712954.1399499047000.221164.1460568985709@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=15239666#comment-15239666 ] 

Aleksey Yeschenko commented on CASSANDRA-7190:
----------------------------------------------

Wouldn't 'the latest schema at the time of the snapshot' just be the schema attached to the most recent sstable though, more or less?

As I see it, this ticket doesn't buy you much over CASSANDRA-9587. Though I don't really mind if you provide a patch and reopen.

bq. Since this is such a LHF, if we could somehow get it into 2.1 and 3.0

Would have to be 3.x only, I'm afraid. Sorry.

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