[
https://issues.apache.org/jira/browse/CASSANDRA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241562#comment-13241562
]
Jeremiah Jordan commented on CASSANDRA-3647:
--------------------------------------------
For the maps/lists/sets, are you talking about a standard way of using
composite columns to implement them, or, a new column type that has a
map/list/set inside one column, and new operations to work with them? Similar
to counters?
I think this Issue started about having a standard way for CQL to store
document attributes in multiple columns using multiple columns and composites
with slices to get/set them.
So if you want to make a standard way of setting up composite columns for
maps/lists/sets, I think this issue can be hi-jacked for that. If you want to
add a new type of column that supports redis like map/set/list operations, I
would make a new issue.
> 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
