[
https://issues.apache.org/jira/browse/CASSANDRA-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405425#comment-13405425
]
Jonathan Ellis edited comment on CASSANDRA-2963 at 7/2/12 11:08 PM:
--------------------------------------------------------------------
I'm a little confused at the new logic in initCf (see CASSANDRA-4402). Is the
idea that we clear out the schema so it can be added back in by gossip, but we
don't want to clear out Table.columnFamilyStores? Why not?
was (Author: jbellis):
I'm a little confused at the new logic in initCf. Is the idea that we
clear out the schema so it can be added back in by gossip, but we don't want to
clear out Table.columnFamilyStores? Why not?
> 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.0
>
> Attachments: CASSANDRA-2963-v3.patch, 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
