[
https://issues.apache.org/jira/browse/CASSANDRA-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840747#action_12840747
]
Gary Dusbabek commented on CASSANDRA-825:
-----------------------------------------
I looked at jug briefly but stopped when I saw native libraries. If there were
a way to use it and extend it so that native bits aren't needed, then I'm +1.
I prefer to avoid introducing native libs if we can avoid it, especially for
something this trivial. I like the 'put something else unique in those bytes'
approach.
2-4 modify introduces DefsTable (similar to SystemTable) as a way to modify
storing and loading the data definitions to the new definitions keyspace.
5 makes it so that cfid generation is safe across restarts and can happen at
times other than startup.
6 gives support for tracking historical CF names. In the case of cf renames,
the id doesn't change, but the name does and we need a way to get back to the
id when recovering.
The basic idea of the set is that we need to add support for reading data
definitions from storage and not xml.
> 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-TimeUUID-generation-and-tests.patch,
> v2-0002-add-MacAddress-to-config.patch,
> v2-0003-dump-and-load-definition-tables.patch,
> v2-0004-make-KSMetaData-immutable.patch,
> v2-0005-push-cfid-generation-down-into-CFMetaData-getting-ri.patch,
> v2-0006-support-for-serializing-historical-cf-names.patch
>
>
> 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.
