Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5DD9018DA0 for ; Thu, 4 Feb 2016 23:38:40 +0000 (UTC) Received: (qmail 89150 invoked by uid 500); 4 Feb 2016 23:38:40 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 89110 invoked by uid 500); 4 Feb 2016 23:38:40 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 89099 invoked by uid 99); 4 Feb 2016 23:38:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Feb 2016 23:38:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D83492C1F6B for ; Thu, 4 Feb 2016 23:38:39 +0000 (UTC) Date: Thu, 4 Feb 2016 23:38:39 +0000 (UTC) From: "Pavel Yaskevich (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-11067) Improve SASI syntax MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133326#comment-15133326 ] Pavel Yaskevich commented on CASSANDRA-11067: --------------------------------------------- [~aweisberg] Thanks for catching that up, modified and pushed! It's always good to have some fresh eyes on it :) > 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)