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) Consider storing types by their CQL names in schema tables instead of fully-qualified internal class names
Date Fri, 09 Oct 2015 13:35:26 GMT

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

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

[~avalanche123] if I got your point, you suspect that UDT and UDF/UDA dependencies might cause
problems resolving dependencies (and thus resulting in unresolved/stale types/UDAs), right?
IMO this (having unresolvable types/UDFs/UDAs) is not related to whether type information
is stored using class names or CQL type signatures.
Generally, the situation is the same for the drivers and for C* internally. AFAIR [~aholmber]'s
point was about parsing CQL types *back* to class-names (_AbstractType_).
Of course, this change is not a trivial thing - neither for C* nor for the drivers.

> Consider storing 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 rc2
>
>
> 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