[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187016#comment-13187016
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
I sympathize with Rackspace's (the employer Eric referred to, for those
following along) desire to build their new rewrite-everything-on-Node.js stack
on CQL, because it *is* much easier than building on Thrift. That goal, we've
delivered on.
But wishing for an alpha-release API to be 100% stable is a level of fantasy
that requires either much more optimism or a much larger ego to think that you
got it THAT right on your first try without ever building anything substantial
on it first, than I'm capable of generating. And we really are talking alpha
here; beta implies feature completness, or close to it.
The users I've talked see clearly that although the ultimate goal does include
stability, an incomplete API is simply not ready to deliver on that. Which is
why you see the overwhelming majority of development still done on "classic"
clients like Hector and pycassa. (And which is why I'm pushing hard to make
CQL3/1.1 feature complete. I do want CQL to succeed, but I'm realistic about
where it stands today.)
Jake and Sylvain's proposal sounds like the only way we're going to be able to
deliver the remaining features we need while still maintaining a compatibility
escape hatch for applications built on early CQL version. But let's be clear:
past 1.1, anyone who wants the old cql package maintained is going to need to
roll up his sleeves and pitch in, because the rest of us have plenty of things
to spend our time on that are more valuable to the community as a whole.
> 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
