[
https://issues.apache.org/jira/browse/CASSANDRA-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133936#comment-15133936
]
Pavel Yaskevich edited comment on CASSANDRA-11067 at 2/5/16 10:17 AM:
----------------------------------------------------------------------
Ok, so maybe we can make supportsExpression for SASI index more dynamic and
return "false" in such case, would it go and try to do a range slice if we do
that?
[~beobal] I've made and pushed that change, so if the mode has is_literal set
and op is RANGE SASIIndex.supportsExpression is going to return false.
was (Author: xedin):
Ok, so maybe we can make supportedOperations for SASI index more dynamic and
return "false" in such case, would it go and try to do a range slice if we do
that?
> 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)
