[ https://issues.apache.org/jira/browse/CASSANDRA-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120697#comment-15120697 ]
Pavel Yaskevich edited comment on CASSANDRA-11067 at 1/28/16 8:09 AM: ---------------------------------------------------------------------- [~beobal] I've updated doc/SASI.md with LIKE support and fixed a typo in Cql.g, also I've noticed that loading of the SASI indexes on startup is missing so I've pushed that too into CASSANDRA-11067 branch (and fixed use of IntervalTree on the way) and rebased everything with the latest trunk. Edit: I've also (just) added ByteBufferUtil.\{startsWith, endsWith\} to complement ByteBufferUtil.contains for LIKE_\{PREFIX, SUFFIX\} accordingly. was (Author: xedin): [~beobal] I've updated doc/SASI.md with LIKE support and fixed a typo in Cql.g, also I've noticed that loading of the SASI indexes on startup is missing so I've pushed that too into CASSANDRA-11067 branch (and fixed use of IntervalTree on the way) and rebased everything with the latest trunk. > 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)