[
https://issues.apache.org/jira/browse/CASSANDRA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406485#comment-13406485
]
Pavel Yaskevich commented on CASSANDRA-3647:
--------------------------------------------
I think I put my position on both points as clear as I could. Somebody else
would have to take a look at this as well, I am not convinced that (at least)
approuch taken for collection representation such as term/value/literal
interconnection is a correct way to go. Code also adds few new types to
o.a.c.db.marshal that make AbstractType even worse interface with new "execute"
operations added.
> Support set and map value types in CQL
> --------------------------------------
>
> Key: CASSANDRA-3647
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3647
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Jonathan Ellis
> Assignee: Sylvain Lebresne
> Labels: cql
> Fix For: 1.2
>
>
> Composite columns introduce the ability to have arbitrarily nested data in a
> Cassandra row. We should expose this through CQL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
