[ https://issues.apache.org/jira/browse/CASSANDRA-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131208#comment-15131208 ]
Jonathan Ellis commented on CASSANDRA-11067: -------------------------------------------- I'm still uneasy about making = a synonym for LIKE. Every database I can think of treats = as full equality. I'm pretty sure that will surprise people. I think we should reject = queries against indexes that aren't going to actually give equality semantics, and require using LIKE instead. (I'm slightly uneasy about overloading LIKE as well, which is why originally I proposed something new like MATCHES. But LIKE already tends to vary from product to product so on balance I'm okay with abusing it a little more.) > 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)