[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185626#comment-13185626
]
Sylvain Lebresne commented on CASSANDRA-2474:
---------------------------------------------
bq. I'm okay with this being inefficient because (as above) it's kind of a
nonsense query.
I can live with that too.
bq. In fact it's probably not much more work than hacking around it in
QueryProcessor
That's true. But since it is, and since all range query end up having a limit,
whether it is the default or not, it's probably better to handle it correctly
since day one. I've created CASSANDRA-3742 to do that. I'm not too far to have
a patch that can be shown, so as soon as I've attached it, I'll deal with
CASSANDRA-3742, unless someone that have a little free time takes it before.
bq. I guess we could just disallow it unless there is also a WHERE clause on
the row key
Right, that's probably good enough on a first shot. I suppose it wouldn't be
crazy to add a reversed option to range slices later but I'm good leaving this
one to later (it's unclear how efficient it will be (to do all those backward
seek) and it's likely a bit more work that the global count thingy).
> 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: 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
