Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 23 Oct 2011 02:13:32 +0000 (UTC)
From: "Yuki Morishita (Commented) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <132484813.6123.1319336012134.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <18867072.12195.1312566327268.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-2997) Enhance human-readability of
 snapshot names created by drop column family
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Yuki Morishita commented on CASSANDRA-2997:
-------------------------------------------

+1 on v2
                
> Enhance human-readability of snapshot names created by drop column family
> -------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2997
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2997
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 0.7.0
>            Reporter: Eric Gilmore
>            Assignee: Yuki Morishita
>            Priority: Minor
>             Fix For: 1.0.1
>
>         Attachments: 0001-Add-CF-name-to-snapshot-dir-when-dropping.patch, 2997-v2.txt
>
>
> Currently when you drop a column family, a snapshot is automatically created in a directory named with the timestamp of the drop.  
> Clever folk will find a way to understand the timestamps and locate particular snapshots, but it is not as effortless as it could be if part or all of the CF name was included in the snapshot name.
> Any strategy to make the snapshot name more user-friendly and easy to find would be helpful.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira