[
https://issues.apache.org/jira/browse/CASSANDRA-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192946#comment-13192946
]
Pavel Yaskevich commented on CASSANDRA-2963:
--------------------------------------------
Now when CASSANDRA-1391 is committed, to reset the schema you will just need to
truncate schema_{keyspaces, columnfamilies, columns} and re-set Schema.instance
to initial (blank) state.
> 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
>
> Attachments: 0001-Add-resetlocalschema-to-nodetool.patch,
> 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
