[
https://issues.apache.org/jira/browse/CASSANDRA-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854004#action_12854004
]
Gary Dusbabek commented on CASSANDRA-827:
-----------------------------------------
Not easily. The current defsVersion needs to be known long before
StorageService (and SystemMetadata) is initialized. I rearranged things so
that DD keeps track of the initial version (from a schema load or whatever) and
passes it to SS. Its all in v3-0009.
I also fixed a rename bug where the replication strategy wasn't getting
reloaded (in case it changed as a result of a drop+add).
> Add hooks that recognize when system KS is updated.
> ---------------------------------------------------
>
> Key: CASSANDRA-827
> URL: https://issues.apache.org/jira/browse/CASSANDRA-827
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Gary Dusbabek
> Assignee: Gary Dusbabek
> Fix For: 0.7
>
> Attachments: v3-0001-remove-unused-JoinMessage.txt,
> v3-0002-Refactor-so-meta-mutations-can-be-serialized-and-moved.txt,
> v3-0003-move-ConfigurationException-to-its-own-class-file.txt,
> v3-0004-Gossip-metadata-version-and-request-updates.txt,
> v3-0005-thrift-changes.txt,
> v3-0006-switch-to-reading-schema-configuration-from-storage.txt,
> v3-0007-thrift-impl.txt, v3-0008-use-cfid-for-all-mutations.txt,
> v3-0009-move-defsVersion-management-into-SystemTable.txt
>
>
> Add hooks that recognize when system KS is updated.
> Figure out the best way to refresh the collections in DD, perform the adds,
> deletes, etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
