[
https://issues.apache.org/jira/browse/CASSANDRA-10380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14903000#comment-14903000
]
Philip Thompson commented on CASSANDRA-10380:
---------------------------------------------
Okay, so then technically we should just close this ticket?
The 2.2 behavior is what we expect in 2.2, because we fixed this in 8099. And
the 3.0 behavior is also expected.
So we should either make this a ticket to document the change, unless we want
to backport it to older versions? But this has been the behavior since long
before 2.2, so I think just having this be a documented change of behavior in
3.0 is acceptable.
> SELECT count within a partition does not respect LIMIT
> ------------------------------------------------------
>
> Key: CASSANDRA-10380
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10380
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Adam Holmberg
> Assignee: Benjamin Lerer
> Priority: Minor
>
> {code}
> cassandra@cqlsh> create KEYSPACE test WITH replication = {'class':
> 'SimpleStrategy', 'replication_factor': '1'};
> cassandra@cqlsh> use test;
> cassandra@cqlsh:test> create table t (k int, c int, v int, primary key (k,
> c));
> cassandra@cqlsh:test> INSERT INTO t (k, c, v) VALUES (0, 0, 0);
> cassandra@cqlsh:test> INSERT INTO t (k, c, v) VALUES (0, 1, 0);
> cassandra@cqlsh:test> INSERT INTO t (k, c, v) VALUES (0, 2, 0);
> cassandra@cqlsh:test> select * from t where k = 0;
> k | c | v
> ---+---+---
> 0 | 0 | 0
> 0 | 1 | 0
> 0 | 2 | 0
> (3 rows)
> cassandra@cqlsh:test> select count(*) from t where k = 0 limit 2;
> count
> -------
> 3
> (1 rows)
> {code}
> Expected: count should return 2, according to limit.
> Actual: count of all rows in partition
> This manifests in 3.0, does not appear in 2.2
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
