cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (CASSANDRA-3647) Support arbitrarily nested "documents" in CQL
Date Mon, 09 Apr 2012 22:11:20 GMT

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

Jonathan Ellis edited comment on CASSANDRA-3647 at 4/9/12 10:11 PM:
--------------------------------------------------------------------

bq. we could very well have a UnionType comparator that takes argument and allow a component
to be one of different comparator 

Maybe.  Note that we never actually need to *compare* the different types, since sub-components
of types X and Y will always have a different parent component.  We just need to *allow* them.

Also, whether the field is a map/list/set is irrelevant for the purposes of the storage engine.
 (All the operations I propose can be done as a single CT insert operation, without read-before-write.
Except for pop, which I didn't think through and I withdraw.)  So not sure whether representing
that as part of the Comparator is the right thing to do.  That is, QueryProcessor will need
to know that some columns should be bundled together as a Map, but ColumnFamilyStore and beneath
won't care.
                
      was (Author: jbellis):
    bq. we could very well have a UnionType comparator that takes argument and allow a component
to be one of different comparator 

Maybe.  Note that we never actually need to *compare* the different types, since sub-components
of types X and Y will always have a different parent component.  We just need to *allow* them.

Also, whether the field is a map/list/set is irrelevant for the purposes of the storage engine.
 (All the operations I propose can be done as a single CT insert operation, without read-before-right.
Except for pop, which I didn't think through and I withdraw. :)  So not sure whether representing
that as part of the Comparator is the right thing to do.  That is, QueryProcessor will need
to know that some columns should be bundled together as a Map, but ColumnFamilyStore and beneath
won't care.
                  
> 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

        

Mime
View raw message