[
https://issues.apache.org/jira/browse/CASSANDRA-12003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329839#comment-15329839
]
Eric Stevens commented on CASSANDRA-12003:
------------------------------------------
In the mailing list it looked like you might be using SASI with LIKE-style
queries ({{WHERE id=2134 AND col1 = '\*value\*'}}), is that the case? If so it
looks like your schema and example case might be incomplete here, so more
details would be helpful.
> 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: 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)
