[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181477#comment-13181477
]
Sylvain Lebresne commented on CASSANDRA-2474:
---------------------------------------------
I'll precise that I was not talking about being intuitive to people coming from
SQL. That's one of those situation where I think that trying to absolutely
stick to SQL syntax syntax should be an absolute goal, not if that means making
Cassandra specificity less clear, because at the end of the day, people will be
using CQL, i.e. Cassandra, *not* SQL. So yes, no SQL database will have a way
to correctly describe our case, but in a way I think that is more a argument
for having a syntax that doesn't exist in SQL, because that makes it clear to
the user that there is a specificity that his worth understanding.
And to avoid having the debate on the wrong thing, I'll note that SECONDARY KEY
is likely a bad name, because secondary key does mean something in the SQL
world (maybe not as a syntax, but it has entries in google at least :)). The
point would be to take something that state explicitly that we differ from SQL,
maybe something like SORTING KEY.
I'll also note that it's not only the sorting itself, as for instance the fact
that (talking my examples above) you can say 'userid IN (...)' but not 'ip IN
(...)' is more intuitive with the SORTING KEY syntax. Same for slices.
bq. PRIMARY KEY syntax is still a good fit for the "you can't update the PK
directly" behavior
True, but that would still be true except that we would add "and you can't
update the SORTING KEY (if any) directly either", which doesn't seem too bad to
me.
> 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
