[CASSANDRA-4493] Fix update of CF comparator (including adding new collections)

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 1.2.0 beta 1
• Severity: Normal
• Assignee: Sylvain Lebresne
• Reporter: Sylvain Lebresne

Authors

Sylvain Lebresne

Reviewers

Jonathan Ellis

• Created: 05/Aug/12 19:22
• Updated: 16/Apr/19 09:32
• Resolved: 07/Sep/12 09:59

Description

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.