Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 20 Nov 2013 14:07:37 +0000 (UTC)
From: "Sylvain Lebresne (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12680285.1384956240398.1157.1384956457797@arcas>
In-Reply-To: <JIRA.12680285.1384956240398@arcas>
References: <JIRA.12680285.1384956240398@arcas>
Subject: [jira] [Created] (CASSANDRA-6383) Secondary indexing of map keys
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sylvain Lebresne created CASSANDRA-6383:
-------------------------------------------

             Summary: Secondary indexing of map keys
                 Key: CASSANDRA-6383
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6383
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Sylvain Lebresne
            Assignee: Sylvain Lebresne
             Fix For: 2.1


CASSANDRA-4511 started adding secondary indexing for collections, but didn't wired map key indexing because this requires generalizing a bit the 2ndary index API to support 2 indexes on the same column. And since that's not entirely related to the initial problem of CASSANDRA-4511, let's tackle this last part here.

I'll note that one other is the syntax. For selection, I propose
{noformat}
SELECT * FROM foo WHERE myMap CONTAINS KEY 'bar';
{noformat}
(but that assumes we use CONTAINS in CASSANDRA-4511, if we use IN, we'll need something else)

For declaring indexes I'm less inspired. We could have something like
{noformat}
CREATE INDEX ON foo(myMap KEYS)
{noformat}
but maybe someone has a better idea?


--
This message was sent by Atlassian JIRA
(v6.1#6144)