You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2013/11/20 15:25:35 UTC

[jira] [Commented] (CASSANDRA-6383) Secondary indexing of map keys

    [ https://issues.apache.org/jira/browse/CASSANDRA-6383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827686#comment-13827686 ] 

Sylvain Lebresne commented on CASSANDRA-6383:
---------------------------------------------

Actually, for the index creation, maybe
{noformat}
CREATE INDEX ON foo(keys(myMap))
{noformat}
could work better in the context of CASSANDRA-6382 (see my comment there).

> 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)