[
https://issues.apache.org/jira/browse/CASSANDRA-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989951#comment-14989951
]
Aleksey Yeschenko commented on CASSANDRA-10365:
-----------------------------------------------
[~slebresne] If you don't really mind, I'll leave it as is *for now*. tbh I
just find v2 conceptually cleaner/simpler. And there might be some value in
having similar logic on both server and in the java-driver. That said, if
drivers team decides to pull the dependency and do something else - I'll revert
too. I'm perfectly fine with revisiting after 3.0.0, and I know Alexandre is
looking at an alternative option as well, so there is a high likelihood that we
will in fact ditch the dependency in both the driver and the server.
Committed with updated bundled as
[340df43fb74f7f3ef021d10ad1b4510636ee3f14|https://github.com/apache/cassandra/commit/340df43fb74f7f3ef021d10ad1b4510636ee3f14]
to 3.0 and merged with trunk, thanks.
No new unit tests are failing. For dtests, will have to do it live on cassci,
now that it's just been updated with the correct driver.
If anything (new) is failing, I'll fix it all today, and won't be closing this
ticket until I'm certain that it's broken nothing.
> 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)
