[
https://issues.apache.org/jira/browse/CASSANDRA-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989830#comment-14989830
]
Sylvain Lebresne commented on CASSANDRA-10365:
----------------------------------------------
bq. It's already being pulled by the driver, and we depend on that
Well, I would argue that it's an even worth idea for the driver to pull a
dependency just for that, but I suppose it's a separate subject. Anyway, I
maintain that I prefer the old version: the new one feels overkill to me and
since I'm not familiar with that new library, I actually have less confidence
in that new version. But it appears to work so you have my opinion and I'll let
you make the final decision.
The rest lgtm.
> Store 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)
