[
https://issues.apache.org/jira/browse/CASSANDRA-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuki Morishita updated CASSANDRA-2963:
--------------------------------------
Attachment: cassandra-1.1-2963-v2.txt
v2 attached.
bq. we don't want to remove data like Schema.init() does just a metadata about
keyspaces/ColumnFamilies;
In v2, Schema.clear only removes metadata. That causes me to modify
Table.initCf to reload metadata. I think the way I did is fine, but please
check.
bq. the better name for Schema.init() would be Schema.clear();
Done.
bq. MigrationManager.resetLocalSchema should propagate IOException
Done.
> Add a convenient way to reset a node's schema
> ---------------------------------------------
>
> Key: CASSANDRA-2963
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2963
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Reporter: Brandon Williams
> Assignee: Yuki Morishita
> Priority: Minor
> Labels: lhf
> Fix For: 1.1.1
>
> Attachments: cassandra-1.1-2963-v2.txt, cassandra-1.1-2963.txt,
> system_reset_schema.txt
>
>
> People often encounter a schema disagreement where just one node is out of
> sync. To get it back in sync, they shutdown the node, move the Schema* and
> Migration* files out of the system ks, and then start it back up. Rather
> than go through this process, it would be nice if you could just tell the
> node to reset its schema.
--
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
