cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2474) CQL support for compound columns
Date Fri, 10 Jun 2011 01:21:59 GMT

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

Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------

bq. Doesn't this limit things to one row key?

Right.  This is fine, because
- row is the unit of what we can do efficiently, multiget causes a lot of foot-shooting
- query-within-row is exactly what you should be using mview rows for anyway, mixing data
from different mviews?  that has a code smell to it

bq. you could use a SQL hint syntax

that doesn't seem nearly as natural to me, and there is no good way distinguish between non-transposed
where expressions (for keys) and transposed (for columns/subcolumns?)

> 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

Mime
View raw message