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 00:55:39 GMT


Jonathan Ellis commented on CASSANDRA-11067:

bq. only if LIKE is used without '%' it means essentially an equals, and "=" is always an
exact match right now.

But you're talking about exact match for search terms, right?  I'm talking about exact match
for the entire column.


SELECT * FROM sasi WHERE bio = 'distributing'

should return zero rows, but

SELECT * FROM sasi WHERE bio = 'Software Engineer, works on the freight distribution at nights
and likes arguing'

should return one row.

If that's how it already works, I apologize for the noise!

> 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