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

Aleksey Yeschenko commented on CASSANDRA-10365:
-----------------------------------------------

bq. That's exactly what I had in mind so lgtm.

Thanks, pushed.

Going through other dtests now. Execution API was not the only thing to change. 
Because of this ticket, metadata API had changes to (to type representations at 
least), but it's all straightforward.

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

Reply via email to