You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Kanthi Subramanian (Jira)" <ji...@apache.org> on 2021/11/27 16:43:00 UTC
[jira] [Assigned] (CASSANDRA-16903) UDTs named after built-in data types
[ https://issues.apache.org/jira/browse/CASSANDRA-16903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kanthi Subramanian reassigned CASSANDRA-16903:
----------------------------------------------
Assignee: (was: Kanthi Subramanian)
> UDTs named after built-in data types
> ------------------------------------
>
> Key: CASSANDRA-16903
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16903
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/UDT
> Reporter: Brandon Bordeaux
> Priority: Normal
> Fix For: 4.0.x
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org