[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182634#comment-13182634
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
The thing is, PRIMARY KEY (X, Y) means that you can have exactly one row with
the given values of X and Y. Which fits perfectly our composite PRIMARY KEY
use case. As an implementation detail it ALSO has effects on sorting, which I
am okay with. PRIMARY KEY (X) SECONDARY KEY (Y) would be flat out wrong in
implying that you can have exactly one row for key X, which I am not okay with.
You'd have to call them something like ENTITY GROUP (X) SECONDARY KEY (Y) and
then explain how that effectively means PRIMARY KEY (X, Y) plus sorting on Y.
I don't really think it's an improvement overall.
> CQL support for compound columns
> --------------------------------
>
> Key: CASSANDRA-2474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
