You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Gary Dusbabek (JIRA)" <ji...@apache.org> on 2010/07/13 20:46:50 UTC
[jira] Commented: (CASSANDRA-1133) utilities for schema
import-from/export-to yaml.
[ https://issues.apache.org/jira/browse/CASSANDRA-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887928#action_12887928 ]
Gary Dusbabek commented on CASSANDRA-1133:
------------------------------------------
+1. Do you plan to change the usage statement in NodeCmd, or is this going to be a hidden feature.
For the record, I no longer think it is worth it to export schema to yaml.
> utilities for schema import-from/export-to yaml.
> ------------------------------------------------
>
> Key: CASSANDRA-1133
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1133
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Gary Dusbabek
> Assignee: Gary Dusbabek
> Priority: Minor
> Fix For: 0.7
>
> Attachments: v1-0001-CASSANDRA-1133.-new-loadSchemaFromYAML-utility.txt
>
>
> SS.loadSchemaFromYaml will be deprecated in 0.8 and removed in 0.8+1. Moving forward, we should have a set of utilities in contrib that maintain the ability to set a schema in yaml and then load it on an empty node.
> If at some point, the higher level clients make it easy to modify the schema, or the CLI becomes a real tool, we probably won't need this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.