[jira] [Commented] (CASSANDRA-11067) Improve SASI syntax

["Dave Brosius (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425619#comment-15425619 ] 

Dave Brosius commented on CASSANDRA-11067:
------------------------------------------

nitpick

PrefixTermTree.search(Expression e)

sanity checks for e == null, but then dereferences it anyway, here  
super.search(e)

maybe just return emptySet() on e == null

> 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
>              Labels: client-impacting, sasi
>             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)