[
https://issues.apache.org/jira/browse/CASSANDRA-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991530#comment-14991530
]
Aleksey Yeschenko commented on CASSANDRA-10365:
-----------------------------------------------
[~slebresne] simple fix
[here|https://github.com/iamaleksey/cassandra/commits/10365-counters-fix], does
the minimal job to handle just supercolumns with counters, and doesn't go any
further (and perhaps shouldn't).
Also, entirely unrelated, but it seems like we do allow counters as map keys,
or at least don't validate it {{RawCollection}} (will follow up after 3.0).
> 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)
