[
https://issues.apache.org/jira/browse/CASSANDRA-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979372#comment-14979372
]
Robert Stupp commented on CASSANDRA-10365:
------------------------------------------
Alright - next try, same branch (force pushed):
* {{system_schema.aggregates.initcond}} is of type {{text}} and contains the
CQL term
* does not (yet) work perfectly due to the issues with
AbstractType/TypeSerializer mentioned above (created CASSANDRA-10617 for this)
* two unit tests in {{AggregationTest}} fail due these issues
* migration of 2.2 UDAs will work fine
> 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
>
>
> 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)
