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

["Joel Knighton (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329547#comment-15329547 ] 

Joel Knighton commented on CASSANDRA-12003:
-------------------------------------------

Is it possible to attach the full schema of this table? Details like column names shouldn't be important, so feel free to anonymize those as appropriate.

> 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
>
>
> On issuing this query:;
> select id,filter_name from navigation_bucket_filter where id=2429 and filter_name='Size_s';
>  id   | filter_name
> ------+----------------------
>  2429 | AdditionalProperty_s
>  2429 |                Brand
> ------------more rows-------
>  2429 |               Size_s
> ------------more rows-------
>  2429 |         sdFullfilled
>  2429 |           sellerCode
> (16 rows)
> Whereas only one result was expected (Row bearing filter_name - Size_s), we got that result but along with 15 other unexpected rows..
> Total number of rows in the partition are 20 (Verified using select id,filter_name from navigation_bucket_filter where id=2429;) 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)