[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180340#comment-13180340
]
Sylvain Lebresne commented on CASSANDRA-2474:
---------------------------------------------
bq. So if we're closing in on consensus on the syntax, the next question is,
how do we represent this in the schema? Do we even bother trying to make it fit
the Thrift schema api?
The only think I see that would need to be added is some column name aliases.
To be more precise, in
{noformat}
CREATE TABLE clicks (
userid uuid,
url text,
timestamp date
PRIMARY KEY (userid, url)
) WITH COMPACT STORAGE
{noformat}
the only thing that is missing for the current schema is that 'column name
alias' is "url". And to support composites we basically need to make that alias
a list. So overall it sounds just like one field for CfDef. Is there something
else I'm missing?
Though to be honest my preference would go to not adding it to CfDef as Thrift
doesn't care about aliase (I would have preferred key_alias was not added to
CfDef for the same reason) but to add to CQL the option to do:
{noformat}
ALTER TABLE foo
ADD PRIMARY KEY (userid, url)
{noformat}
for those upgrading from thrift. Not that I feel really strongly about it
though.
bq. I'd take CQL-only at this point if that helps us get it into 1.1.
I'm happily volunteering to work on this and to start now, unless someone else
feels strongly about doing this one (and unless someone object to the consensus
on the syntax). But at the risk of sounding like a buzzkill, I'd mention that
this will be tight and I don't think we should rush this (both code and
review). That being said, if there is no hiccup with the implementation we may
be good.
> 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: Pavel Yaskevich
> 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
