cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11067) Improve SASI syntax
Date Thu, 04 Feb 2016 03:49:39 GMT


Jonathan Ellis commented on CASSANDRA-11067:

I see.  I think I'm okay with that.  Again, if you want to avoid that, you can use LIKE instead,
which will change behavior to match the index by design.  Whereas equals does not, also by

Re the prior art, I think that where the behavior of databases and search systems conflict,
we should prefer to act like a database.  I also note that Solr uses "q=term" syntax but this
is saying the *query* is this term, not the *document* which is what we're talking about here.
 And ES uses "match" in all the examples I could find.

> Improve SASI syntax
> -------------------
>                 Key: CASSANDRA-11067
>                 URL:
>             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

View raw message