[
https://issues.apache.org/jira/browse/CASSANDRA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250261#comment-13250261
]
Jonathan Ellis commented on CASSANDRA-3647:
-------------------------------------------
Those are good ideas, but I'm going to be the bad guy in the name of keeping
this in-scope for 1.2. :)
The crucial idea here is to provide *nested* collections for convenience; if
it's so big you need to page it, it probably belongs in a separate row. So
paging is not on my short list to start with.
I also chose the word "list" over "deque" because I cannot think of a way to
provide push-front efficiently (i.e., without read-before-write, and without
update-all-existing-list-items). As I mentioned in passing, we can provide
append efficiently by using v1 uuids as column names (and translating to list
indexes in QueryProcessor), but that doesn't give us anything else for "free."
Open to suggestions if you have a better design in mind, of course.
> Support arbitrarily nested "documents" 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
