[
https://issues.apache.org/jira/browse/CASSANDRA-10365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991544#comment-14991544
]
Sylvain Lebresne commented on CASSANDRA-10365:
----------------------------------------------
bq. simple fix here, does the minimal job to handle just supercolumns with
counters
That's exactly what I had in mind so lgtm.
bq. it seems like we do allow counters as map keys, or at least don't validate
it {{RawCollection}}
Saw that too and not sure why that is. Seems like an oversight though maybe we
check some place else. We'll have to check.
> 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)
