[jira] [Commented] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.
[
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080640#comment-14080640
]
Krzysztof Zarzycki commented on CASSANDRA-7636:
---
I confirm that the patch works!
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
Assignee: Marcus Eriksson
Fix For: 2.1.0
Attachments: 0001-actually-filter-the-cached-result.patch
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)
[jira] [Commented] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.
[
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080642#comment-14080642
]
Marcus Eriksson commented on CASSANDRA-7636:
bq. it has to go through review and then you'll add it to the new RC, right?
correct
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
Assignee: Marcus Eriksson
Fix For: 2.1.0
Attachments: 0001-actually-filter-the-cached-result.patch
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)
[jira] [Commented] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.
[
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080947#comment-14080947
]
Aleksey Yeschenko commented on CASSANDRA-7636:
--
LGTM, +1
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
Assignee: Marcus Eriksson
Fix For: 2.1.0
Attachments: 0001-actually-filter-the-cached-result.patch
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)
[jira] [Commented] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.
[
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080114#comment-14080114
]
Krzysztof Zarzycki commented on CASSANDRA-7636:
---
OK, I investigated the issue more deeply and came up with a very simple
reproducing example. I rewrote the description completely according to what I
found. I hope it would be clear now where the bug is.
[~brandon.williams], here I paste the output of tracing of the query.
Unfortunately, it's pretty poor and does not give much of details.
{code}
cqlsh:test_keyspace select * from test where p1 = 123 and c1 10;
p1 | c1
-+
123 | 10
(1 rows)
Tracing session: 4be8e9d0-183b-11e4-b8f4-9b0bde0fbcd8
activity
| timestamp | source| source_elapsed
--++---+
Execute
CQL3 query | 2014-07-31 00:46:08.365000 | 127.0.0.1 | 0
Parsing select * from test where p1 = 123 and c1 10 LIMIT 1;
[SharedPool-Worker-3] | 2014-07-31 00:46:08.365000 | 127.0.0.1 | 42
Preparing statement
[SharedPool-Worker-3] | 2014-07-31 00:46:08.365000 | 127.0.0.1 | 74
Request complete | 2014-07-31 00:46:08.365218 | 127.0.0.1 |218
{code}
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? 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}
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)
[jira] [Commented] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.
[
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080126#comment-14080126
]
Brandon Williams commented on CASSANDRA-7636:
-
Doesn't repro for me against 2.1.0-HEAD:
{noformat}
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;
(0 rows)
cqlsh:test_keyspace
{noformat}
Not sure what fixed it, though.
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? 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}
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)
[jira] [Commented] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.
[
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080157#comment-14080157
]
Krzysztof Zarzycki commented on CASSANDRA-7636:
---
Dammit, do you know when a new candidate would be released? I wanted to run
cassandra 2.1 on production as I hoped RC versions are already pretty stable.
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)
[jira] [Commented] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.
[
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080183#comment-14080183
]
Brandon Williams commented on CASSANDRA-7636:
-
There are currently two issues to close, then a new rc. But I did try this
against rc4 now too, and still it didn't repro following your example to the
letter.
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)
[jira] [Commented] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.
[
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080208#comment-14080208
]
Krzysztof Zarzycki commented on CASSANDRA-7636:
---
And I did try my example against cassandra-2.1 branch and I reproduced the
issue. So it seems like there is something specific with my environment that
causes issues...
Let's try to enumerate it:
- I create a table with caching by WITH caching = '{keys:NONE,
rows_per_partition:ALL}';
- The cluster was upgraded from version 2.0.8 and now I have cassandra-2.1.0-rc4
- I run it on Oracle JDK 1.8
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)
[jira] [Commented] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.
[
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.
[
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080282#comment-14080282
]
Brandon Williams commented on CASSANDRA-7636:
-
You're exactly right, nice catch. I can repro now and I took your example a
little further and this looks fairly serious:
{noformat}
cqlsh:test_keyspace select * from test where p1 = 123 and c1 ;
p1 | c1
-+
123 | 10
123 | 20
(2 rows)
{noformat}
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)
[jira] [Commented] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.
[
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080285#comment-14080285
]
Brandon Williams commented on CASSANDRA-7636:
-
Definitely related to row cache since if you restart without a saved cache you
get this:
{noformat}
cqlsh:test_keyspace select * from test where p1 = 123 and c1 ;
p1 | c1
+
(0 rows)
cqlsh:test_keyspace select * from test where p1 = 123 and c1 ;
p1 | c1
-+
123 | 10
123 | 20
(2 rows)
{noformat}
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
Fix For: 2.1.0
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)
