[
https://issues.apache.org/jira/browse/CASSANDRA-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841292#action_12841292
]
Gary Dusbabek commented on CASSANDRA-825:
-----------------------------------------
CLH maps ids to dirty bits and flush points--no names. If we modified RM to
contain a name->id map, we'd be in good shape and could get rid of the
historical names.
What I've done (and don't care for) in 840 is modify the CF during recovery if
it is detected that the name has changed (can't find an id). This is
error-prone because if a user has a habit of recycling cfnames over time, the
reverse mapping can become ambiguous.
I'll make a change so that the cfid can be had from the RM as opposed to table.
> 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.
