[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185603#comment-13185603
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
bq. {{SELECT * FROM Events WHERE event_type IN (e1, e2) LIMIT 500;}}
I'm okay with this being inefficient because (as above) it's kind of a nonsense
query.
bq. {{SELECT * FROM Events LIMIT 1000}}
As you say, this one is relatively straightforward to add an efficient
implementation of. In fact it's probably not much more work than hacking
around it in QueryProcessor (range query for keys first, then page through the
rows one at a time to avoid OOMing), but I'm fine ignoring optimization here as
well -- this is probably *the* most common query interactively, but not
something you'd find in an actual application.
> 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
