[
https://issues.apache.org/jira/browse/CASSANDRA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292781#comment-13292781
]
Sylvain Lebresne commented on CASSANDRA-3647:
---------------------------------------------
Forgot to mention a few stuffs.
Currently the result to a query is returned to thrift as JSON (so as a string
in JSON format). For sets, it actually returns a list since json has no support
of sets.
Also, the only supported way to query is to query for the full list/map/set. I
suppose that we could later had more ways to query, like:
{noformat}
SELECT L[1] FROM ...; -- select list element by index
SELECT M["foo"] FROM ...; -- select specific map elements
SELECT S["a":"z"] FROM ...; -- select a slice of a set (since after all our
sets and maps are sorted)
{noformat}
But none of this is implemented yet (and I'm keen on pushing that to a follow
up ticket).
> 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
