[
https://issues.apache.org/jira/browse/CASSANDRA-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450005#comment-13450005
]
Jonathan Ellis commented on CASSANDRA-4493:
-------------------------------------------
+1
> Fix update of CF comparator (including adding new collections)
> --------------------------------------------------------------
>
> Key: CASSANDRA-4493
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4493
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 1.2.0
>
> Attachments: 0001-Flush-after-CFStore-reload.txt,
> 0002-Fix-ALTER-logic.txt
>
>
> Updating the comparator of a column family (which is authorized if the new
> comparator is "compatible" with the old one, and that includes adding a new
> component to a CompositeType, or adding a new collection to a CQL3 table)
> doesn't completely work. The problem is that even if we change the comparator
> in CFMetada, the old comparator will still be aliased by the current
> memtable. This means updates (that expect the new comparator) will fail until
> a new memtable is created.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
