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

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 3.0 alpha 1
• Severity: Low
• Assignee: Aleksey Yeschenko
• Reporter: Aleksey Yeschenko

Authors

Aleksey Yeschenko

Reviewers

Tom Hobbs

• Created: 15/Jul/15 17:36
• Updated: 16/Apr/19 09:31
• Resolved: 17/Jul/15 22:10

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() + ")"));

Issue Links

• links to: GitHub branch