[CASSANDRA-6383] Secondary indexing of map keys

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.1 beta1
• Component/s: Feature/2i Index, Legacy/CQL
• Assignee: Sylvain Lebresne Assign to me
• Reporter: Sylvain Lebresne

Authors

Sylvain Lebresne

Reviewers

Aleksey Yeschenko

• Created: 20/Nov/13 14:04
• Updated: 16/Apr/19 09:31
• Resolved: 08/Jan/14 13:35

Description

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

SELECT * FROM foo WHERE myMap CONTAINS KEY 'bar';

(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

CREATE INDEX ON foo(myMap KEYS)

but maybe someone has a better idea?

Issue Links

• requires: CASSANDRA-4511 Secondary index support for CQL3 collections

Sub-Tasks

• Add "CREATE INDEX ... ON ..(KEYS())" syntax to cqlsh and CQL.textile: Resolved