[
https://issues.apache.org/jira/browse/CASSANDRA-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952785#comment-14952785
]
Sylvain Lebresne commented on CASSANDRA-10365:
----------------------------------------------
bq. I think it is doable, but if keeping both is possible, it'd make the driver
upgrades that much easier.
I certainly understand that argument, but the fully-qualified class names are
also leaking implementation details, namely which concrete classes are used
server side. On the long term, removing that leakage is probably a good idea
and might allow some cleanups of type classes at some point, and since we've
redone the whole schema table, that sounds like a good time to do so. So while
I understand this is a bit more work for the drivers (mostly, you'd have to
either make sure you're up-to-date on types before querying columns, or resolve
the types you don't know about by querying afterwards), I do feel that not
conserving the fqcn version in new tables is the right thing to do.
> 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)
