[
https://issues.apache.org/jira/browse/CASSANDRA-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132368#comment-15132368
]
DOAN DuyHai commented on CASSANDRA-11067:
-----------------------------------------
I agree with Jonathan POV wrt the semantics of {{=}}.
Let me rephrase it with some example:
As an user, when issuing {{WHERE name='John'}} with SASI, I expect:
\\
\\
* If the index on name is case-insensitive, SASI should return rows having
{{'John'}} or {{'john'}} or {{'joHn'}} etc...
* Else SASI should return rows having exactly {{'John'}}
In both cases (case-sensitive or not), I don't expect SASI to return me
{{'Johnathan'}} (with extra characters at the end) or {{'Leejohn'}} (extra
characters at the beginning) etc ...
[~xedin], *what combination of options configurations can give me the above
behaviour* ? {{SPARSE}} mode ? {{NORMAL}} (formerly called PREFIX) mode without
any analyzer ?
> Improve SASI syntax
> -------------------
>
> Key: CASSANDRA-11067
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11067
> Project: Cassandra
> Issue Type: Task
> Components: CQL
> Reporter: Jonathan Ellis
> Assignee: Pavel Yaskevich
> Fix For: 3.4
>
>
> I think everyone agrees that a LIKE operator would be ideal, but that's
> probably not in scope for an initial 3.4 release.
> Still, I'm uncomfortable with the initial approach of overloading = to mean
> "satisfies index expression." The problem is that it will be very difficult
> to back out of this behavior once people are using it.
> I propose adding a new operator in the interim instead. Call it MATCHES,
> maybe. With the exact same behavior that SASI currently exposes, just with a
> separate operator rather than being rolled into =.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
