[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187038#comment-13187038
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
bq. CQL has been 1.0 since 0.8. That's not alpha.
The 1.0 designation was Eric's. I didn't push back because I remembered when
he said this:
bq. the only reason to fuss about a 1.0, is that it is loaded with special
meaning. To impart some vague notion of readiness on people who should be
paying less attention to a number, and doing more due diligence.
I also take this part of the CQL docs to mean that a X.Y version number implies
no stability or maturity, only levels of compatibility:
{noformat}
Versioning of the CQL language adheres to the "Semantic
Versioning":http://semver.org guidelines. Versions take the form X.Y.Z where
X, Y, and Z are integer values representing major, minor, and patch level
respectively.
{noformat}
In any case, a rose by any other name would smell as sweet, and calling an
incomplete, untested API 1.0 doesn't make it non-alpha.
> 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
