[
https://issues.apache.org/jira/browse/CASSANDRA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288667#comment-13288667
]
Jonathan Ellis commented on CASSANDRA-3647:
-------------------------------------------
bq. Not sure that we can really support lists meaningfully
I think I'm leaning back towards supporting lists again. While we can't do
random-access against lists, none of the document databases out there do
either; fetching L[3] fetches all of L, and updating L[3] = foo rewrites all of
L.
And having syntactic sugar for a Map whose keys are timeuuids is just very
useful syntactic sugar.
So if we make this explicit -- that the operations allowed are simply
appending, fetching the entire list, and overwriting the entire list (which we
can do by writing a composite tombstone, plus the new list items) then I think
we're in good shape.
> 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
> Labels: cql
>
> 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
