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 17FAD18CE5 for ; Thu, 24 Sep 2015 04:46:05 +0000 (UTC) Received: (qmail 32147 invoked by uid 500); 24 Sep 2015 04:46:04 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 32113 invoked by uid 500); 24 Sep 2015 04:46:04 -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 32102 invoked by uid 99); 24 Sep 2015 04:46:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Sep 2015 04:46:04 +0000 Date: Thu, 24 Sep 2015 04:46:04 +0000 (UTC) From: "Sam Tunnicliffe (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-10214) Enable index selection to be overridden on a per query basis 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-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-10214: ---------------------------------------- Fix Version/s: (was: 3.x) 3.0.0 rc2 > Enable index selection to be overridden on a per query basis > ------------------------------------------------------------ > > Key: CASSANDRA-10214 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10214 > Project: Cassandra > Issue Type: New Feature > Reporter: Sam Tunnicliffe > Assignee: Sam Tunnicliffe > Fix For: 3.0.0 rc2 > > > (Broken out of CASSANDRA-10124) > We could add a {{USING INDEX }} clause to {{SELECT}} syntax to force the choice of index and bypass the usual index selection mechanism. > {code} > CREATE TABLE ks.t1(k int, v1 int, v2 int, PRIMARY KEY (k)); > CREATE INDEX v1_idx ON ks.t1(v1); > CREATE INDEX v2_idx ON ks.t1(v2); > CREATE CUSTOM INDEX v1_v2_idx ON ks.t1(v1, v2) USING 'com.foo.bar.CustomMultiColumnIndex'; > # Override internal index selection mechanism > SELECT * FROM ks.t1 WHERE v1=0 AND v2=0 USING INDEX v1_idx; > SELECT * FROM ks.t1 WHERE v1=0 AND v2=0 USING INDEX v2_idx; > SELECT * FROM ks.t1 WHERE v1=0 AND v2=0 USING INDEX v1_v2_idx; > {code} > This is in some ways similar to [index hinting|http://docs.oracle.com/cd/B19306_01/server.102/b14211/hintsref.htm#CHDJDIAH] in Oracle. > edit: fixed typo's (missing INDEX in the USING clauses) -- This message was sent by Atlassian JIRA (v6.3.4#6332)