cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bhuvan Rawal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12003) Not filtering Data completely when where clause is applied to clustering column
Date Tue, 14 Jun 2016 18:01:27 GMT

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

Bhuvan Rawal updated CASSANDRA-12003:
-------------------------------------
    Attachment: lucene_index.cql

> 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)

Mime
View raw message