cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7771) Allow multiple 2ndary index on the same column
Date Tue, 12 May 2015 19:54:02 GMT


Aleksey Yeschenko commented on CASSANDRA-7771:

bq. This is marked as requiring 6717, is that absolutely a blocker?

Yes, it's an absolute blocker. The dumb-ass way we store index info currently only lets us
have one index per column (and if we don't have any, 3 extra tombstones in {{schema_columnfamilies}}
per every column).

Indexes info should live in a separate {{schema.indexes}} table, so that we no longer have
those ridiculous tombstones, and can have multiple indexes on a column. 

> Allow multiple 2ndary index on the same column
> ----------------------------------------------
>                 Key: CASSANDRA-7771
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Sylvain Lebresne
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>             Fix For: 2.2.x
> Currently, the code assumes that we'll only have one 2ndary index per column. This has
been reasonable so far but stop being it with CASSANDRA-6382 (you might want to index multiple
fields of the same UDT column) and CASSANDRA-7458 (you may want to have one "normal" index
an multiple functional index for the same column). So we should consider removing that assumption
in the code, which is mainly 2 places:
> # in the schema: each ColumnDefinition only has infos for one index. This part should
probably be tackled in CASSANDRA-6717 so I'm marking this issue as a follow-up of CASSANDRA-6717.
> # in the 2ndary index API: this is the part I'm suggesting we fix in this issue.

This message was sent by Atlassian JIRA

View raw message