cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2474) CQL support for compound columns
Date Mon, 19 Dec 2011 20:39:32 GMT


Sylvain Lebresne commented on CASSANDRA-2474:

For the sparse example:
CREATE TABLE timeline (
    userid int primary key,
    posted_at uuid,
    posted_by int,
    body text
) TRANSPOSED AS (posted_at), SPARSE(posted_by, body);
Not sure I'm very fond of that. The fact that the type of 'posted_by' and 'body' are actually
not the type of the component itself but the type of the value while they do correspond to
an actual component means that:
# you have not way to give the type of that last component; and if it's not text, the notation
won't look so nice.
# the notation only work if the 'sparse' component is the last one, which may be the case
for "transposition of super columns", but feels arbitrarily limited otherwise.

I think that the fact that 'posted_by' and 'body' are actually string literals is not very
intuitive and only mildly consistent with the rest of the syntax.

I'd also note that as far as I can tell, we wouldn't be able to handle the dynamic composite
type with this in a meaningful way. But as you said above, this can be handled by a destructuring
syntax. Which I think we definitively need.
> CQL support for compound columns
> --------------------------------
>                 Key: CASSANDRA-2474
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Eric Evans
>            Assignee: Pavel Yaskevich
>              Labels: cql
>             Fix For: 1.1
>         Attachments: screenshot-1.jpg, screenshot-2.jpg
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message