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

Jonathan Ellis edited comment on CASSANDRA-2474 at 6/10/11 6:22 PM:
--------------------------------------------------------------------

bq. you can specify the following column mappings in cassandra.columns.mapping

Okay, I get it.  The reason there is no explanation of WHERE and resultsets is 
because these are not supported, for the reason deduced above in the N*M 
explanation.
 
So you are limited to the number of levels of nesting that you have magic names 
for?

bq. you are going to be doing a map reduce on most/all the data anyway

The right way to represent a "select * from foo" with no compound modification 
is to present it with compound keys (in the SQL sense not in the sense of 
"multiple keys crammed into a single value"):

{noformat}
rowkey columnkey     subcol1    subcol2
key1         col1    val1       val2
key1         col2    v3         v4
{noformat}


      was (Author: jbellis):
    bq. you can specify the following column mappings in 
cassandra.columns.mapping

So you are limited to the number of levels of nesting that you have magic names 
for?

bq. you are going to be doing a map reduce on most/all the data anyway

The right way to represent a "select * from foo" with no compound modification 
is to present it with compound keys (in the SQL sense not in the sense of 
"multiple keys crammed into a single value"):

{noformat}
rowkey columnkey     subcol1    subcol2
key1         col1    val1       val2
key1         col2    v3         v4
{noformat}

  
> CQL support for compound columns
> --------------------------------
>
>                 Key: CASSANDRA-2474
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API, Core
>            Reporter: Eric Evans
>              Labels: cql
>             Fix For: 1.0
>
>
> For the most part, this boils down to supporting the specification of 
> compound column names (the CQL syntax is colon-delimted terms), and then 
> teaching the decoders (drivers) to create structures from the results.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to