You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Krzysztof Zarzycki (JIRA)" <ji...@apache.org> on 2014/07/31 00:43:38 UTC

[jira] [Updated] (CASSANDRA-7636) Data is not filtered out when using WHERE clause on cluster column

     [ 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_id<0 >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)