[
https://issues.apache.org/jira/browse/CASSANDRA-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757917#action_12757917
]
Jonathan Ellis commented on CASSANDRA-44:
-----------------------------------------
Yes, describing renames is a minor problem (with ZK too).
We could add JMX commands for managing CFs but then you get back to the Bad Old
Days of having this xml around that is overridden by "invisible" information in
the system table.
I would just add an attribute e.g. MigrateFrom to the CF definition that says
"here's what the old name was, rename the data files when you move to the new
definition."
<ColumnFamily name="Standard82" migratefrom="Standard1" ...>
(Note that I only suggest splitting this into a separate file for clarity, not
because it's somehow inherent to manage-by-re-parse.)
> It is difficult to modify the set of ColumnFamliies in an existing cluster
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-44
> URL: https://issues.apache.org/jira/browse/CASSANDRA-44
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Eric Evans
> Fix For: 0.5
>
>
> ColumnFamilies may be added when cassandr is not running by editing the
> configuration file.
> If you need to delete or re-order CFs, you must
> 1) kill cassandra
> 2) start it again and wait for log replay to finish
> 3) kill cassandra AGAIN
> 4) make your edits (now there is no data in the commitlog)
> 5) manually remove the sstable files (-Data.db, -Index.db, and -Filter.db)
> for the CFs you removed, and rename files for CFs you renamed
> 6) start cassandra and your edits should take effect
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
