[CASSANDRA-16903] UDTs named after built-in data types

• Type: Bug
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Fix Version/s: 4.0.x
• Component/s: Feature/UDT
• Bug Category: Correctness
• Severity: Normal
• Complexity: Normal
• Discovered By: User Report
• Platform: All
• Assignee: Unassigned
• Reporter: Brandon Bordeaux
• Created: 31/Aug/21 15:54
• Updated: 27/Nov/21 16:42

Description

Working with Cassandra 4.0 I found UDTs can be named after some built-in data type, like map, list, and tuple, but not for other types, like text or set. This behavior should be consistent across all built-in types where Cassandra shouldn't allow a UDT to be named after any built-in type.

Having UDTs named after built-in types cause confusion working with table schemas and may introduce downstream issues when Cassandra works with these types.