[
https://issues.apache.org/jira/browse/CASSANDRA-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14975377#comment-14975377
]
Aleksey Yeschenko commented on CASSANDRA-10365:
-----------------------------------------------
The third (in-progress) commit switches types in schema tables to their
canonical CQL representation. That includes changes to 'functions' and
'aggregates' tables to no longer keep a surrogate {{signature}} column.
Only non-nested (in anything) UDTs are supported there. Unfortunately there is
an annoying bug in {{TypeParser}} that breaks down for some type that don't
even involve UDT's (think {{frozen<map<frozen<set<int>>,
frozen<list<int>>>>}}). Need a bit more time to resolve that.
In the meantime, this unblocks drivers work/critical path.
> 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)
