[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186970#comment-13186970
]
T Jake Luciani commented on CASSANDRA-2474:
-------------------------------------------
bq. we're proposing making these changes late in the 11th hour of the release
cycle, and without seeking input from the wider community
I don't understand. You emailed the community for input, we created a wiki
explaining the options. We've run out of paint for the bikeshed. Now that the
work is being done we need to go back and re-explain the issue?
Have we stated either way to the community that the current form of CQL is
going to be backwards compatible? I understand that its the end goal but we are
not there yet. If it was considered *done* why are we discussing handling wide
rows in the first place?
I think the best option here is to keep the old cql around in whatever form it
currently is and start fresh with this transposed approach. If/When the
current users get around to changing syntax then we can drop it.
</badcop>
> CQL support for compound columns and wide rows
> ----------------------------------------------
>
> 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
> Priority: Critical
> Labels: cql
> Fix For: 1.1
>
> Attachments: 0001-Add-support-for-wide-and-composite-CFs.patch,
> 0002-thrift-generated-code.patch, 2474-transposed-1.PNG,
> 2474-transposed-raw.PNG, 2474-transposed-select-no-sparse.PNG,
> 2474-transposed-select.PNG, cql_tests.py, 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
