cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2474) CQL support for compound columns
Date Tue, 10 Jan 2012 17:32:40 GMT


Eric Evans commented on CASSANDRA-2474:

bq. Now if I'm the only one to think that maybe the PK notation may end up being more confusing
than helpful and does not convey important notion specific to C*, then I'll shut up.

FWIW, I agree with you in principle.  I've been involved in several such discussions in the
past and have always felt that strict adherence to SQL syntax without adherence to SQL semantics
was a double-edged sword. It's great that it leverages what people already know, until it
doesn't work they way they _know_ it should.

But those discussions are in the past (where were you then? :)), and convention has since
become to adopt SQL syntax where possible, even if semantics differ.

What differs here is the degree by which this has the potential to surprise people, and I
do think this sets a precedence in that regard.
> CQL support for compound columns
> --------------------------------
>                 Key: CASSANDRA-2474
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Eric Evans
>            Assignee: Sylvain Lebresne
>              Labels: cql
>             Fix For: 1.1
>         Attachments: 2474-transposed-1.PNG, 2474-transposed-raw.PNG, 2474-transposed-select-no-sparse.PNG,
2474-transposed-select.PNG, raw_composite.txt, 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