[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180522#comment-13180522
]
Eric Evans commented on CASSANDRA-2474:
---------------------------------------
bq. 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.
I also think this is tight, particularly since it's introducing new syntax, and
a syntax that required one of the most (if not _the_ most) epic discussions.
Ever.
I've been thinking about this for a while, but what do people think about
implementing an experimental mode? Something that involves setting a boolean
in {{cassandra.conf}}, or passing a {{-Dcassandra.experimental=true}} property.
Code like this (or prepared statements for that matter) could test that
experimental mode is enabled, or raise a new Thrift exception if it isn't.
Granted that means we'll see less testing than we would otherwise, but I think
we stand to see more/better testing than we would from a beta or RC. More
importantly, it sets an expectation that it's new, less tested, and that
breaking changes might be coming (all of which are true IMO).
> 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
