[
https://issues.apache.org/jira/browse/CASSANDRA-7017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236748#comment-15236748
]
Alex Petrov commented on CASSANDRA-7017:
----------------------------------------
I've made the corresponding changes, waiting for the CI results now:
|[trunk|https://github.com/ifesdjeen/cassandra/tree/7017-followup-trunk]|[dtest|http://cassci.datastax.com/job/ifesdjeen-7017-followup-trunk-dtest/1/]|[testall|http://cassci.datastax.com/job/ifesdjeen-7017-followup-trunk-testall/1/]|
> allow per-partition LIMIT clause in cql
> ---------------------------------------
>
> Key: CASSANDRA-7017
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7017
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Halliday
> Assignee: Alex Petrov
> Labels: cql
> Fix For: 3.6
>
> Attachments: 0001-Allow-per-partition-limit-in-SELECT-queries.patch,
> 0001-Allow-per-partition-limit-in-SELECT-queriesV2.patch,
> 0001-CASSANDRA-7017.patch
>
>
> somewhat related to static columns (#6561) and slicing (#4851), it is
> desirable to apply a LIMIT on a per-partition rather than per-query basis,
> such as to retrieve the top (most recent, etc) N clustered values for each
> partition key, e.g.
> -- for each league, keep a ranked list of users
> create table scores (league text, score int, player text, primary key(league,
> score, player) );
> -- get the top 3 teams in each league:
> select * from scores staticlimit 3;
> this currently requires issuing one query per partition key, which is tedious
> if all the key partition key values are known and impossible if they aren't.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
