cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CASSANDRA-1133) utilities for schema import-from/export-to yaml.
Date Fri, 23 Jul 2010 20:27:52 GMT

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

Brandon Williams edited comment on CASSANDRA-1133 at 7/23/10 4:27 PM:
----------------------------------------------------------------------

bin/schematool is not executable, and also invokes the now renamed LoadSchema class, +1 with
those changes.

      was (Author: brandon.williams):
    bin/schematool is not executable, and also invokes the now renamed LoadSchema class
  
> 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.0
>
>         Attachments: 0002-tool-to-export-schema.patch, 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.


Mime
View raw message