[
https://issues.apache.org/jira/browse/CASSANDRA-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131479#comment-15131479
]
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.
So,
{code}
SELECT * FROM sasi WHERE bio = 'distributing'
{code}
should return zero rows, but
{code}
SELECT * FROM sasi WHERE bio = 'Software Engineer, works on the freight
distribution at nights and likes arguing'
{code}
should return one row.
If that's how it already works, I apologize for the noise!
> 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)
