Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 24 Feb 2014 14:49:20 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12678433.1384062968692.92231.1393253360464@arcas>
In-Reply-To: <JIRA.12678433.1384062968692@arcas>
References: <JIRA.12678433.1384062968692@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-6326) Snapshot should create
 manifest file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis edited comment on CASSANDRA-6326 at 2/24/14 2:47 PM:
--------------------------------------------------------------------

I thought we're talking about the manifest file used by LCS.  If we're not, any snapshot-processing tools you create in-house are welcome to throw around a list of files involved but I'm not sure that belongs in the C* server.


was (Author: jbellis):
I thought we're talking about the manifest file used by LCS.

> Snapshot should create manifest file 
> -------------------------------------
>
>                 Key: CASSANDRA-6326
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6326
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: sankalp kohli
>            Assignee: sankalp kohli
>            Priority: Minor
>
> We should create a manifest file as part of the snapshot which should contain all the stables included in the snapshot. 
> This will be very important for systems consuming this snapshot as they can validate the fact that they got the complete snapshot. 
> If Cassandra crashes mid way creating a snapshot, I think it will create an incomplete snapshot. 


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)