[jira] [Commented] (CASSANDRA-3647) Support arbitrarily nested "documents" in CQL

["Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249933#comment-13249933 ] 

Jonathan Ellis commented on CASSANDRA-3647:
-------------------------------------------

bq. 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.

Well, it's both.  Because we do want the latter, but implemented as the former.  I suppose it's reasonable to split out CQL operations (list append/pop, map get/put/remove, set add/remove) to another ticket.

So first, we're going to need to support heterogeneous comparators somehow.  Consider this table declaration:

{code}
CREATE TABLE foo (
    id int PRIMARY KEY,
    field1 text,
    field2 map<int, text>,
    field3 list<text>
);
{code}

The Cassandra CF containing these rows will contain single-level columns ({{field1}}), CT(ascii, int) ({{field2}}), and CT(ascii, uuid) ({{field3}}), assuming that we represent lists with v1 uuid column names, which seems like the best option to me.

CASSANDRA-3657 gets us part of the way there (all CF column names will have the same prefix, which is the CQL column name) but not all the way.


                
> 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