[
https://issues.apache.org/jira/browse/CASSANDRA-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953362#comment-14953362
]
Adam Holmberg commented on CASSANDRA-10365:
-------------------------------------------
If the concern is about leaking implementation details, would it be reasonable
to instead store User Types as fully-specified abstract types as we do in the
results encoding?
https://github.com/apache/cassandra/blob/trunk/doc/native_protocol_v4.spec#L607-L618
I know this is not CQL, but it would avoid having to resolve inner types.
> 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)
