[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179070#comment-13179070
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
bq. I would prefer CREATE COMPACT TABLE ... it's a property of the definition
itself (that cannot be changed) rather than of that specific 'body' field. It
also make the rule for COMPACT table rather simple: "a compact table should
have only one field not part of the primary key"; you don't have to deal with
errors like someone defining two VALUE() for instance.
Those are good points. Personally I'd still rather have a "WITH COMPACT
STORAGE" syntax *after* CREATE TABLE ( ... ), since that's a more general way
to tackle nonstandard options.
bq. I think we have 4 different cases
You nailed it, that's exactly what I want to solve here.
bq. Random other ideas
As you say, let's leave these as future work for now, this is a big enough
discussion as it is. :)
> 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
