[
https://issues.apache.org/jira/browse/CASSANDRA-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215702#comment-15215702
]
Olivier Michallat commented on CASSANDRA-11067:
-----------------------------------------------
Using the Java driver for example:
{code}
PreparedStatement pst = session.prepare("select * from test.users where
first_name LIKE ?");
BoundStatement bs = pst.bind("Jon%");
{code}
The first line fails with {{SyntaxError: line 1:47 mismatched input '?'
expecting STRING_LITERAL}} (which makes sense since it's how it's declared in
the grammar). Other operators declare the right-hand side value as a
{{Term.Raw}}, which can also be a bind marker.
I think users will expect to be able to bind the argument this way.
> 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
> 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)
