cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7771) Allow multiple 2ndary index on the same column
Date Fri, 21 Aug 2015 14:36:47 GMT


Jeremiah Jordan commented on CASSANDRA-7771:

bq. Never mind that the exception message is written in parseltongue, this is the correct
behaviour that we should preserve.

Agreed.  We should force someone to use an index name for any 2nd/3rd/4th index added.  I
think we should do that even if the 1st created index did not use the default name.

> Allow multiple 2ndary index on the same column
> ----------------------------------------------
>                 Key: CASSANDRA-7771
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Sylvain Lebresne
>            Assignee: Sam Tunnicliffe
>              Labels: client-impacting
>             Fix For: 3.0 beta 1
> 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