[
https://issues.apache.org/jira/browse/CASSANDRA-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980714#comment-14980714
]
Sylvain Lebresne commented on CASSANDRA-10365:
----------------------------------------------
bq. Its presence doesn't bother me much - it's still huge savings all over -
now that we don't need to read the previous state at all
I don't dispute that, and while I suspect we might be able to avoid it, it
actually doesn't really bother me. The lack of comment does bother me however
given that it looks fishy without context.
> 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
>
>
> 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)
