[CASSANDRA-10721] Altering a UDT might break UDA deserialisation

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.4, 3.4
• Component/s: Legacy/CQL, Legacy/Distributed Metadata
• Severity: Normal
• Since Version: 3.0.0
• Assignee: Robert Stupp
• Reporter: Aleksey Yeschenko

Authors

Robert Stupp

Reviewers

Benjamin Lerer

• Created: 17/Nov/15 15:08
• Updated: 16/Apr/19 09:30
• Resolved: 17/Feb/16 11:01

Description

CASSANDRA-10650 switched UDA's initcond serialisation in schema to its CQL literal. This means that if any particular field is renamed in the UDT, or of its type gets changes, we will not be able to parse initcond back.

We should either:
1) Forbid renames and type switches in UDTs that are being used in UDAs, or
2) Make sure we alter the UDAs in schema alongside the new UDT at all times

Issue Links

• is broken by: CASSANDRA-10650 Store UDA initcond as CQL literal in the schema table, instead of a blob
• relates to: CASSANDRA-10723 Rewrite INITCOND after renames and alters of UDT fields
• links to: Git branch