You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Bhuvan Rawal (JIRA)" <ji...@apache.org> on 2016/06/14 18:37:27 UTC

[jira] [Issue Comment Deleted] (CASSANDRA-12003) Not filtering Data completely when where clause is applied to clustering column

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

Bhuvan Rawal updated CASSANDRA-12003:
-------------------------------------
    Comment: was deleted

(was: Also one of the non primary key columns (which is not present in Stratio index as well) is a JSON Map which is serialized and kept as text. This field may go upto 16MB in the extreme case for a row cell normally in KB . But things were working fine in 3.0.3.)

> Not filtering Data completely when where clause is applied to clustering column
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-12003
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12003
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local Write-Read Paths
>         Environment: Production
>            Reporter: Bhuvan Rawal
>             Fix For: 3.8
>
>         Attachments: lucene_index.cql, table_schema_not_filtering.cql
>
>
> On issuing this query:;
> select id,col1 from table where id=2134 and col1='clust_key1';
>  id   | col1
> ------+----------------------
>  2429 | clust_key2
>  2429 |                clust_key3
> ------------more rows-------
>  2429 |               clust_key1
> ------------more rows-------
>  2429 |         clust_key4
>  2429 |           clust_key5
> (16 rows)
> Whereas only one result was expected (Row bearing col1 - clust_key1), we got that result but along with 15 other unexpected rows..
> Total number of rows in the partition are 20 (Verified using select id,col1 from table where id=2134; ) as well as json dump. We are wondering why Cassandra could not filter the results completely. I have checked that the data is intact by taking json dump and validating using sstabledump tool. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)