[
https://issues.apache.org/jira/browse/CASSANDRA-16903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432977#comment-17432977
]
Benjamin Lerer commented on CASSANDRA-16903:
--------------------------------------------
In my opinion there are 2 possible approaches to fix it:
* at the ANTLR parser level by reorganizing and changing the logic surrounding
{{unreserved_function_keyword}} and {{basic_unreserved_keyword}}
* Within {{CreateFunctionStatement}} and {{CreateAggregateStatement}} by
rejecting the names the we do not want.
The ANTLR solution sound like the better one to me. As the logic surrounding
accepted name for functions is already there.
> 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: Kanthi Subramanian
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
