[jira] [Commented] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.

2014-07-31 Thread Krzysztof Zarzycki (JIRA) 

[ 
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] [Comment Edited] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.

2014-07-31 Thread Krzysztof Zarzycki (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080640#comment-14080640
 ] 

Krzysztof Zarzycki edited comment on CASSANDRA-7636 at 7/31/14 8:23 AM:


I confirm that the patch works! Thank you:)

Now I understand it has to go through review and then you'll add it to the new 
RC, right?


was (Author: zarzyk):
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] [Updated] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column

2014-07-30 Thread Krzysztof Zarzycki (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krzysztof Zarzycki updated CASSANDRA-7636:
--

Description: 

I have a table on which I'm running some SELECTs with WHERE clause filtering on 
cluster columns, but the rows are not getting filtered out. 

Look: 
cqlsh:leadbullet create KEYSPACE test_keyspace WITH replication = {'class': 
'SimpleStrategy', 'replication_factor': 1};
cqlsh:leadbullet 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 = 1395139215166955 and c1  10;

(0 rows)

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)

The filtering on other (partition) columns runs fine. Only the clustering 
column is somewhat malfunctioning. 


  was:
I encountered a weird, invalid situation with my cluster. I have a table on 
which I'm running some SELECTs with WHERE clause filtering on cluster columns, 
but the rows are not getting filtered out. 
Look: 
 select * from page_view where website_id = xxx and user_id = 'some_user' and 
page_id =0; -- tried also page_id0 0

 website_id | user_id   | page_id  | ...
+---+--+
xxx | some_user | 21044533 | ...
...more rows here, none with page_id=0

The filtering on other (partition) columns runs fine. Only the clustering 
column is somewhat malfunctioning. 

Important is, how I got to this table:
1. I collected data with Cassandra version 2.0.8
2. I snapshotted the data, and removed the main copy from cluster's data.
3. I upgraded cluster to version 2.1.0-rc4
4. I've recreated the schema of tables in new version.
5. I ran sstableloader on the data to load data to new upgraded cluster.
6. I spotted the problem with filtering.
7. I've tried to run nodetool repair, nodetool upgradesstables -a , neither 
helped. 

I'm not deleting the invalid data. I'm eager to help investigating the issue if 
someone instructs me how to do it. 


 Data is not filtered out when using WHERE clause on cluster column
 --

 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

 I have a table on which I'm running some SELECTs with WHERE clause filtering 
 on cluster columns, but the rows are not getting filtered out. 
 Look: 
 cqlsh:leadbullet create KEYSPACE test_keyspace WITH replication = {'class': 
 'SimpleStrategy', 'replication_factor': 1};
 cqlsh:leadbullet 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 = 1395139215166955 and c1  
 10;
 (0 rows)
 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)
 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] [Updated] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column

2014-07-30 Thread Krzysztof Zarzycki (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krzysztof Zarzycki updated CASSANDRA-7636:
--

Description: 
I have a table on which I'm running some SELECTs with WHERE clause filtering on 
cluster columns, but the rows are not getting filtered out. 

Look: 
cqlsh:leadbullet create KEYSPACE test_keyspace WITH replication = {'class': 
'SimpleStrategy', 'replication_factor': 1};
cqlsh:leadbullet 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)

The filtering on other (partition) columns runs fine. Only the clustering 
column is somewhat malfunctioning. 


  was:

I have a table on which I'm running some SELECTs with WHERE clause filtering on 
cluster columns, but the rows are not getting filtered out. 

Look: 
cqlsh:leadbullet create KEYSPACE test_keyspace WITH replication = {'class': 
'SimpleStrategy', 'replication_factor': 1};
cqlsh:leadbullet 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 = 1395139215166955 and c1  10;

(0 rows)

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)

The filtering on other (partition) columns runs fine. Only the clustering 
column is somewhat malfunctioning. 



 Data is not filtered out when using WHERE clause on cluster column
 --

 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

 I have a table on which I'm running some SELECTs with WHERE clause filtering 
 on cluster columns, but the rows are not getting filtered out. 
 Look: 
 cqlsh:leadbullet create KEYSPACE test_keyspace WITH replication = {'class': 
 'SimpleStrategy', 'replication_factor': 1};
 cqlsh:leadbullet 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)
 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] [Updated] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.

2014-07-30 Thread Krzysztof Zarzycki (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krzysztof Zarzycki updated CASSANDRA-7636:
--

Summary: Data is not filtered out when using WHERE clause on cluster column 
on Column Family with row cache on.  (was: Data is not filtered out when using 
WHERE clause on cluster column)

 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

 I have a table on which I'm running some SELECTs with WHERE clause filtering 
 on cluster columns, but the rows are not getting filtered out. 
 Look: 
 cqlsh:leadbullet create KEYSPACE test_keyspace WITH replication = {'class': 
 'SimpleStrategy', 'replication_factor': 1};
 cqlsh:leadbullet 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)
 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] [Updated] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.

2014-07-30 Thread Krzysztof Zarzycki (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krzysztof Zarzycki updated CASSANDRA-7636:
--

Description: 
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. 


  was:
I have a table on which I'm running some SELECTs with WHERE clause filtering on 
cluster columns, but the rows are not getting filtered out. 

Look: 
cqlsh:leadbullet create KEYSPACE test_keyspace WITH replication = {'class': 
'SimpleStrategy', 'replication_factor': 1};
cqlsh:leadbullet 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)

The filtering on other (partition) columns runs fine. Only the clustering 
column is somewhat malfunctioning. 



 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] [Updated] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.

2014-07-30 Thread Krzysztof Zarzycki (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krzysztof Zarzycki updated CASSANDRA-7636:
--

Description: 
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. 


  was:
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. 



 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.

2014-07-30 Thread Krzysztof Zarzycki (JIRA) 

[ 
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] [Updated] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.

2014-07-30 Thread Krzysztof Zarzycki (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krzysztof Zarzycki updated CASSANDRA-7636:
--

Description: 
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. 


  was:
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. 



 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.

2014-07-30 Thread Krzysztof Zarzycki (JIRA) 

[ 
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.

2014-07-30 Thread Krzysztof Zarzycki (JIRA) 

[ 
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] [Comment Edited] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.

2014-07-30 Thread Krzysztof Zarzycki (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080208#comment-14080208
 ] 

Krzysztof Zarzycki edited comment on CASSANDRA-7636 at 7/30/14 11:46 PM:
-

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, but I've tried running on openjdk 1.7 and had the 
same effect




was (Author: zarzyk):
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.

2014-07-30 Thread Krzysztof Zarzycki (JIRA) 

[ 
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] [Comment Edited] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column on Column Family with row cache on.

2014-07-30 Thread Krzysztof Zarzycki (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080271#comment-14080271
 ] 

Krzysztof Zarzycki edited comment on CASSANDRA-7636 at 7/31/14 12:14 AM:
-

[~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 clean config from repo, 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.


was (Author: zarzyk):
[~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] [Created] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column

2014-07-29 Thread Krzysztof Zarzycki (JIRA) 
Krzysztof Zarzycki created CASSANDRA-7636:
-

 Summary: Data is not filtered out when using WHERE clause on 
cluster column
 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


I encountered a weird, invalid situation with my cluster. I have a table on 
which I'm running some SELECTs with WHERE clause filtering on cluster columns, 
but the rows are not getting filtered out. 
Look: 
 select * from page_view where website_id = xxx and user_id = 'some_user' and 
page_id =0; -- tried also page_id0 0

 website_id | user_id   | page_id  | ...
+---+--+
xxx | some_user | 21044533 | ...
...more rows here, none with page_id=0

The filtering on other (partition) columns runs fine. Only the clustering 
column is somewhat malfunctioning. 

Important is, how I got to this table:
1. I collected data with Cassandra version 2.0.8
2. I snapshotted the data, and removed the main copy from cluster's data.
3. I upgraded cluster to version 2.1.0-rc4
4. I've recreated the schema of tables in new version.
5. I ran sstableloader on the data to load data to new upgraded cluster.
6. I spotted the problem with filtering.
7. I've tried to run nodetool repair, nodetool upgradesstables -a , neither 
helped. 

I'm not deleting the invalid data. I'm eager to help investigating the issue if 
someone instructs me how to do it. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)