[
https://issues.apache.org/jira/browse/CASSANDRA-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14951339#comment-14951339
]
Bulat Shakirzyanov commented on CASSANDRA-10365:
------------------------------------------------
Just to clarify, the issue is that when we see a
"org.apache.cassandra.db.marshal.UserType", it contains all information about
its fields. Whereas when reading users.address, we will have to lookup the
definition of that UDT separately, which may or may not be present in the
driver's schema metadata. This might complicate the process of constructing
schema metadata, especially considering that we still have to support previous
versions of Cassandra that used fqcn style types. I think it is doable, but if
keeping both is possible, it'd make the driver upgrades that much easier.
> 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)
