cassandra-commits mailing list archives

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


Jonathan Ellis commented on CASSANDRA-2474:

1. materialized view is a way of thinking about it, I'm not saying we require declaring special
mview metadata (I would like to, but I think people will want "manual" control)
3. I like that idea
4. not sure what you mean.  SQL is about "give me this projection, from this relation, where
this predicate is satisfied."  putting it in the FROM (relation) part requires the least special
casing for the rest (projection + predicate look normal).  Since the relation part is the
logical part for QueryProcessor to determine "am I doing a transposed query?" it simplifies
implementation too.
5. yes, you'd get the full range of expressivity, limited only by what the engine can handle
(e.g., in my first example, the current supercolumn engine doesn't index subcolumns so "AND
x > 100" would not be efficient).  but you can see how this gives us room to add more power
w/o needing more syntax or special casing in the parser.

> CQL support for compound columns
> --------------------------------
>                 Key: CASSANDRA-2474
>                 URL:
>             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:

View raw message