You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Manish M Pillai (Jira)" <ji...@apache.org> on 2024/09/02 13:20: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 ]

Manish M Pillai reassigned CASSANDRA-16903:
-------------------------------------------

    Assignee: Manish M Pillai

> 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
>            Assignee: Manish M Pillai
>            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.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org