cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10365) Store types by their CQL names in schema tables instead of fully-qualified internal class names
Date Thu, 05 Nov 2015 16:01:27 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991869#comment-14991869
] 

Robert Stupp commented on CASSANDRA-10365:
------------------------------------------

Well, you're right and I'm right ;)
10365 introduced NPEs on {{DROP TABLE (IF EXISTS)}} and throws {{ConfigurationException}}
on {{DROP AGGREGATE/FUNCTION IF EXISTS}}.
2.1 and 2.2 are also affected by {{InvalidRequestException}} for {{DROP TYPE IF EXISTS}}
(opened CASSANDRA-10658)

> 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)

Mime
View raw message