[
https://issues.apache.org/jira/browse/CASSANDRA-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131575#comment-15131575
]
Jonathan Ellis commented on CASSANDRA-11067:
--------------------------------------------
bq. The problem which that approach is some of the tokenization doesn't cause
changes to internal structure of the text so requiring always to use "=" is not
aways adequate.
Not sure what you mean. You can always use {{LIKE 'term'}} where you could use
{{= 'term'}}, right? So just use LIKE and leave = for untokenized (and
numeric) comparison.
bq. I would say we need to let indexing implementations decide what ops to
support and how to support them, because "=" for tokenized/stemmed results is a
norm.
Where is = the norm? Jon gave a good summary above for LIKE behavior, I can
add that none of those systems overload = for tokenization.
> 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)
