You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2015/06/30 02:34:05 UTC

[jira] [Commented] (CASSANDRA-9677) Refactor KSMetaData

    [ https://issues.apache.org/jira/browse/CASSANDRA-9677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606738#comment-14606738 ] 

Aleksey Yeschenko commented on CASSANDRA-9677:
----------------------------------------------

For (1), pushed a commit to https://github.com/iamaleksey/cassandra/commit/cca674a5e47a75a664a891318f28fdfe7a6a4dd3 (on top of CASSANDRA-9665 changes).

> Refactor KSMetaData
> -------------------
>
>                 Key: CASSANDRA-9677
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9677
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>             Fix For: 3.x
>
>
> As part of CASSANDRA-9425 and a follow-up to CASSANDRA-9665, and a pre-requisite for new schema change protocol, this ticket will do the following
> 1. Make {{UTMetaData}} immutable (new {{Types}} class)
> 2. Refactor handling of the {{CFMetaData}} map in {{KSMetaData}} (new {{Tables}} class)
> 3. Factor out params into a separate class ({{KeyspaceParams}})
> 4. Rename and move {{KSMetaData}} to {{schema.KeyspaceMetadata}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)