cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Bordeaux (Jira)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-16903) UDTs named after built-in data types
Date Tue, 31 Aug 2021 15:55:00 GMT
Brandon Bordeaux created CASSANDRA-16903:
--------------------------------------------

             Summary: 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


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.3.4#803005)

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


Mime
View raw message