[CASSANDRA-12746] Wrong search results if clustering column has SASI index

• Type: Bug
• Status: Resolved
• Priority: Urgent
• Resolution: Duplicate
• Labels: sasi
• Severity: Critical
• Assignee: Unassigned
• Reporter: Mikhail Krupitskiy
• Created: 04/Oct/16 17:18
• Updated: 16/Apr/19 09:30
• Resolved: 17/Nov/16 14:51

Description

Cassandra 3.5.

Code snippet to reproduce the issue:

DROP keyspace if exists kmv;
CREATE keyspace if not exists kmv WITH REPLICATION = { 'class' : 'SimpleStrategy', 'replication_factor':'1'} ;
USE kmv;

CREATE TABLE if not exists kmv (id int, c1 text, PRIMARY KEY(id,c1));

CREATE CUSTOM INDEX ON kmv.kmv  ( c1 ) USING 'org.apache.cassandra.index.sasi.SASIIndex' WITH OPTIONS = {
'analyzed' : 'true',
'analyzer_class' : 'org.apache.cassandra.index.sasi.analyzer.NonTokenizingAnalyzer',
'case_sensitive' : 'false', 
'mode' : 'CONTAINS'
};

INSERT into kmv (id, c1) values (1, 'qweasd') ;
INSERT into kmv (id, c1) values (1, 'uuu') ;
INSERT into kmv (id, c1) values (2, 'qwe') ;

c1 is a clustering column with SASI index.
An attempt to add a restriction for partition key AND for the clustering column leads to incorrect results:

SELECT c1 from kmv.kmv where id=1 and c1 like '%qwe%';

Expected results:
qweasd
Actual results:
qweasd, uuu

Looks like a restriction for c1 was ignored.

Issue Links

• duplicates: CASSANDRA-12674 [SASI] Confusing AND/OR semantics for StandardAnalyzer
• is duplicated by: CASSANDRA-12785 LIKE query with partition key restriction gives unexpected results