[
https://issues.apache.org/jira/browse/CASSANDRA-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719829#action_12719829
]
Jonathan Ellis commented on CASSANDRA-44:
-----------------------------------------
Or if we are using ZK (for instance) to hold CF definitions such that we can
keep the index/CF map there and not re-use indexes for deleted CFs then we can
rely on the commitlog ordering always being valid (and just check to make sure
we don't replay into a decomissioned CF).
> It isn't possible to easily add new column families to an existing cluster
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-44
> URL: https://issues.apache.org/jira/browse/CASSANDRA-44
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Eric Evans
> Fix For: 0.4
>
>
> Once a cluster is created, adding new column families to the configuration
> file will not result in their creation. See also:
> http://groups.google.com/group/cassandra-dev/browse_thread/thread/78598f808e10b984/fe26cae1689d5474
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
