[
https://issues.apache.org/jira/browse/CASSANDRA-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991805#comment-14991805
]
Aleksey Yeschenko commented on CASSANDRA-10365:
-----------------------------------------------
[~snazy] I'm not sure that this patch belongs here at all. It's not correcting
post-10365 behavior, it's changing semantics of {{DROP IF EXISTS}}. Previously,
when dropping a type or a function with {{IF EXISTS}}, we were still throwing
if the keyspace itself was missing, no?
Either way, please open a separate ticket, as I'm not sure this is directly
relevant.
> Store types by their CQL names in schema tables instead of fully-qualified
> internal class names
> -----------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-10365
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10365
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Labels: client-impacting
> Fix For: 3.0.0
>
>
> Consider saving CQL types names for column, UDF/UDA arguments and return
> types, and UDT components.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
