[
https://issues.apache.org/jira/browse/CASSANDRA-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900489#comment-13900489
]
Sylvain Lebresne edited comment on CASSANDRA-6701 at 2/13/14 4:43 PM:
----------------------------------------------------------------------
Attaching trivial patch. I've pushed the example above as a dtest too.
Btw, the patch kind of fix another small issue in that in the example above,
results ended-up not ordered following the IN order, which we do it otherwise
(since there is no ORDER BY on c1, only on c2).
was (Author: slebresne):
Attaching trivial patch. I've pushed the example above as a dtest too.
> IN on the last clustering columns + ORDER BY DESC yield no results
> ------------------------------------------------------------------
>
> Key: CASSANDRA-6701
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6701
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 1.2.16
>
> Attachments: 6701.txt
>
>
> That's not a very common mix but well, the following return no results which
> is obviously bogus:
> {noformat}
> CREATE TABLE test (k int, c1 int, c2 int, PRIMARY KEY (k, c1, c2));
> INSERT INTO test(k, c1, c2) VALUES (0, 0, 0);
> INSERT INTO test(k, c1, c2) VALUES (0, 0, 1);
> INSERT INTO test(k, c1, c2) VALUES (0, 0, 2);
> SELECT * FROM test WHERE k=0 AND c1 = 0 AND c2 IN (2, 0) ORDER BY c1 DESC
> {noformat}
> Note: it's pretty useless to order on a column which has an equal
> restriction, and that's probably why nobody ran into this yet, but that's
> really just due to a minor typo so there is no reason not to fix.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
