[
https://issues.apache.org/jira/browse/CASSANDRA-11397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208987#comment-15208987
]
Jordan West commented on CASSANDRA-11397:
-----------------------------------------
[~beobal] the patch looks good and i've confirmed your fix locally. One small
piece of feedback: since you fixed things to return a
{{ClusteringIndexSliceFilter}} I don't think the {{isLike}} check in
{{PrimaryKeyRestrictionSet#appendTo}} is necessary anymore (i've removed it
locally without issue).
> LIKE query on clustering column index returns incorrect results
> ---------------------------------------------------------------
>
> Key: CASSANDRA-11397
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11397
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Labels: sasi
> Fix For: 3.5
>
>
> The way that {{ClusteringIndexFilter}} and {{RowFilter}} are constructed when
> a {{LIKE}} restriction on a clustering column is present is incorrect. For
> example:
> {code}
> cqlsh> create table ks.t1 (k text, c1 text, c2 text, c3 text, v text, primary
> key (k,c1,c2,c3));
> cqlsh> create custom index on ks.t1(c2) using
> 'org.apache.cassandra.index.sasi.SASIIndex';
> cqlsh> select * from ks.t1;
> k | c1 | c2 | c3 | v
> ---+----+----+----+-----
> a | ba | ca | da | val
> a | bb | cb | db | val
> a | bc | cc | dc | val
> (3 rows)
>
> cqlsh> select * from ks.t1 where c1 = 'ba' and c3 = 'da' and c2 LIKE 'c%'
> ALLOW FILTERING;
> k | c1 | c2 | c3 | v
> ---+----+----+----+---
> (0 rows)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
