You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2014/07/29 15:24:38 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14077701#comment-14077701 ]
Brandon Williams commented on CASSANDRA-7636:
---------------------------------------------
As a first step, perhaps tracing the query would shed some light.
> 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_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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)