[
https://issues.apache.org/jira/browse/CASSANDRA-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841201#action_12841201
]
Gary Dusbabek commented on CASSANDRA-825:
-----------------------------------------
> - for patch 5, why do we need historical names?
I might be missing something, but the cfname is one of the serialized
properties of RowMutation that ends up in the commit log. Since it would be a
lot of work to flush the commit log prior to a rename, we need away to get from
the old cfnames to the current id. It doesn't have anything to do with old
sstables.
> Create an additional system keyspace to store KS definitions and migration
> data.
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-825
> URL: https://issues.apache.org/jira/browse/CASSANDRA-825
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: Gary Dusbabek
> Assignee: Gary Dusbabek
> Priority: Minor
> Fix For: 0.7
>
> Attachments:
> v2-0001-CASSANDRA-825-use-jug-for-TimeUUID-generation.txt,
> v2-0002-dump-and-load-definition-tables.txt,
> v2-0003-make-KSMetaData-immutable.txt,
> v2-0004-push-cfid-generation-down-into-CFMetaData-getting-rid-.txt,
> v2-0005-support-for-serializing-historical-cf-names.txt
>
>
> Create an additional system keyspace to store KS definitions and migration
> data.
> Tweak the internals so cassandra can optional load all definitions from
> there, ignoring CF definitions in the xml.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
