Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 26 May 2011 16:03:47 +0000 (UTC)
From: "David Boxenhorn (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1998988169.45608.1306425827667.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <207503240.9202.1298406698903.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-2221) 'show create' commands on the
 CLI to export schema
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

David Boxenhorn commented on CASSANDRA-2221:
--------------------------------------------

That's a very minimal amount of diffing, whether the CF exists or not! 

> 'show create' commands on the CLI to export schema
> --------------------------------------------------
>
>                 Key: CASSANDRA-2221
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2221
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Jeremy Hanna
>            Assignee: Aaron Morton
>            Priority: Minor
>              Labels: cli
>             Fix For: 0.8.1
>
>         Attachments: 0001-add-show-schema-statement-8.patch, 0001-add-show-schema-statement.patch
>
>
> It would be nice to have 'show create' type of commands on the command-line so that it would generate the DDL for the schema.
> A scenario that would make this useful is where a team works out a data model over time with a dev cluster.  They want to use parts of that schema for new clusters that they create, like a staging/prod cluster.  It would be very handy in this scenario to have some sort of export mechanism.
> Another use case is for testing purposes - you want to replicate a problem.
> We currently have schematool for import/export but that is deprecated and it exports into yaml.
> This new feature would just be able to 'show' - or export if they want the entire keyspace - into a script or commands that could be used in a cli script.  It would need to be able to regenerate everything about the keyspace including indexes and metadata.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira