[
https://issues.apache.org/jira/browse/CASSANDRA-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133308#comment-15133308
]
Ariel Weisberg commented on CASSANDRA-11067:
--------------------------------------------
[~xedin] I think the [docs
here|https://github.com/xedin/cassandra/blob/ed37504ad38bd85c6bcdeba637eda382a1f69b79/doc/SASI.md#equality--prefix-queries]
may still be slightly off WRT to LIKE vs '=' and the current state of the
world.
{quote}
The semantics of CQL's = were modified instead of making further modifications
of the grammar with the introduction of a LIKE operator. Ideally, CQL would be
modified to include such an operator, supporting both prefix and suffix
searches.
{quote}
> 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)
