You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Bulat Shakirzyanov (JIRA)" <ji...@apache.org> on 2015/10/06 19:02:26 UTC

[jira] [Commented] (CASSANDRA-10365) Consider storing types by their CQL names in schema tables instead of fully-qualified internal class names

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

Bulat Shakirzyanov commented on CASSANDRA-10365:
------------------------------------------------

I think this is a very useful metadata to include. My only suggestion is to keep the old representation (fqcn) as well. Currently drivers use this representation to detect type information. Parsing CQL-only representation might not be robust for the reasons mentioned in https://issues.apache.org/jira/browse/CASSANDRA-6717#comment-14791788.


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