[
https://issues.apache.org/jira/browse/CASSANDRA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293025#comment-13293025
]
Jonathan Ellis commented on CASSANDRA-3647:
-------------------------------------------
bq. if you do 2 update with a literal in the same millisecond, you won't end up
with one or the other, but rather as a merge of both literals
That's pretty tough to explain without leaking implementation details, but I
guess 1.2 will still be a net win in that respect if we cut out supercolumns. :)
bq. the only supported way to query is to query for the full list/map/set
IMO this is a Good Thing, we don't want to encourage people stuffing their
entire model into a single row since that breaks our partitioning assumptions.
> 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
