[CASSANDRA-9816] ALTER TABLE ADD validation is overly strict for re-added collection columns - ASF JIRA

Agile Board

Attach files

Attach Screenshot

Bulk Copy Attachments

Bulk Move Attachments

Voters

Watch issue

Watchers

Create sub-task

Convert to sub-task

Move

Link

Clone

Labels

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Low
Resolution: Fixed
Fix Version/s: 3.0 alpha 1
Component/s: None
Labels:
None

Severity:
Low

Description

AlterTableStatement ensures that we cannot re-add a collection column of a type that is incompatible with a previously existing, dropped one.

It doesn't make an exception, however, for frozen collections, yet those should be allowed.

Code in question:

if (dropped != null && (dropped.type == null || (dropped.type instanceof CollectionType && !type.isCompatibleWith(dropped.type))))
    throw new InvalidRequestException(String.format("Cannot add a collection with the name %s " +
                "because a collection with the same name and a different type%s has already been used in the past",
                columnName, dropped.type == null ? "" : " (" + dropped.type.asCQL3Type() + ")"));