[
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080271#comment-14080271
]
Krzysztof Zarzycki commented on CASSANDRA-7636:
-----------------------------------------------
[~brandon.williams] I probably know, why you can't reproduce. You probably
haven't enabled row cache in cassandra.yaml (or by jmx) by setting some
non-zero size to it.
I just created a fresh cluster with cache disabled, issue didn't show up. Then
enabled the cache and issue showed up.
So finally, for me: it looks like a bug in source code, definitely.
> Data is not filtered out when using WHERE clause on cluster column on Column
> Family with row cache on.
> ------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-7636
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7636
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 2.1.0-rc4
> Reporter: Krzysztof Zarzycki
>
> My pretty simplified case looks like the following:
> I create a table with partition and cluster column. I set key caching to NONE
> and row caching to ALL.
> When I'm running some SELECTs with WHERE clause filtering on cluster columns,
> the rows sometimes are not getting filtered out. When? Probably when the row
> gets loaded to row cache (By some previous query).
> Look at this scenario:
> {code}
> cqlsh:xxx> create KEYSPACE test_keyspace WITH replication = {'class':
> 'SimpleStrategy', 'replication_factor': 1};
> cqlsh:xxx> use test_keyspace ;
> cqlsh:test_keyspace> CREATE TABLE test (p1 bigint, c1 int, PRIMARY KEY (p1,
> c1) ) WITH caching = '{"keys":"NONE", "rows_per_partition":"ALL"}';
> cqlsh:test_keyspace> insert into test (p1, c1 ) values ( 123, 10);
> cqlsh:test_keyspace> select * from test where p1 = 123 and c1 > 10;
> (0 rows)
> cqlsh:test_keyspace> select * from test where p1 = 123 and c1 > 9;
> p1 | c1
> -----+----
> 123 | 10
> (1 rows)
> cqlsh:test_keyspace> select * from test where p1 = 123 and c1 > 10;
> p1 | c1
> -----+----
> 123 | 10
> (1 rows)
> {code}
> Running the same scenario, but with row cache turned OFF works fine.
> The filtering on other (partition) columns runs fine. Only the clustering
> column is somewhat malfunctioning.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
