[
https://issues.apache.org/jira/browse/CASSANDRA-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131272#comment-15131272
]
Pavel Yaskevich commented on CASSANDRA-11067:
---------------------------------------------
bq. I'm still uneasy about making = a synonym for LIKE. Every database I can
think of treats = as full equality. I'm pretty sure that will surprise people.
But the LIKE is not a synonym for "=", only if LIKE is used without '%' it
means essentially an equals, and "=" is always an exact match right now. Also I
would like to point out that all of the index types in SASI support strict
equality (current "=") because even CONTAINS mode does preserve the original
word form, so I'm not even sure what is the problem because each index has
supportedOperations check and if one of the implementations doesn't support
strict equality it's going to be rejected because even LIKE '<term>' is
transformed to EQ, which forces users to do LIKE with '%' which can only be
PREFIX, CONTAINS or SUFFIX.
> 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)
