[
https://issues.apache.org/jira/browse/CASSANDRA-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119654#comment-15119654
]
Jack Krupansky commented on CASSANDRA-11067:
--------------------------------------------
Thanks, [~slebresne], for opening that separate issue. My apologies for taking
advantage of the vague and general wording of the title/summary of this
particular Jira. I had considered making my suggestions on the original ticket,
but didn't when I saw that it was already "closed" and this one is suggestively
labeled "Improve SASI syntax" (rather than "Restore = semantics for SASI".)
Again, sorry for the distraction from getting SASI done for 3.4 ASAP.
> 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)
