[
https://issues.apache.org/jira/browse/CASSANDRA-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Dusbabek updated CASSANDRA-1087:
-------------------------------------
Attachment: 0001-load-schema-from-schema.yaml-if-on-the-classpath.patch
0002-remove-loadSchemaFromYaml-from-StorageServiceMBean.patch
* modifies converter to create schema.yaml
* loads schema.yaml if no schema is defined and schema.yaml is found on the CP
* does away with StorageServiceMBean.loadSchemaFromYaml
ACHTUNG!
Only do this on a single node. Additional nodes will receive their schema from
the cluster. If you do this on subsequent nodes Bad Things will happen.
Bad Things: the new node will have a different migrationId than the rest of the
cluster and will continually receive requests to push these migrations out
since the other nodes think they are running old schemas. These migrations
will fail since the keyspaces they instruct to add already exist
> load schema from schema.yaml or schema.xml if no schema is present and
> definition file exists in the classpath.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-1087
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1087
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Gary Dusbabek
> Assignee: Gary Dusbabek
> Fix For: 0.7
>
> Attachments:
> 0001-load-schema-from-schema.yaml-if-on-the-classpath.patch,
> 0002-remove-loadSchemaFromYaml-from-StorageServiceMBean.patch
>
>
> While I'm at it, this would be a good time to update
> http://wiki.apache.org/cassandra/API to include documentation about the
> system_* calls.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
