[CASSANDRA-10127] Make naming for secondary indexes consistent

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.0 rc1
• Component/s: Feature/2i Index, Legacy/CQL, Legacy/Tools
• Severity: Normal
• Assignee: Benjamin Lerer
• Reporter: Sam Tunnicliffe

Authors

Benjamin Lerer

Reviewers

T Jake Luciani

• Created: 19/Aug/15 14:37
• Updated: 16/Apr/19 09:30
• Resolved: 03/Sep/15 19:42

Description

We have a longstanding mismatch between the name of an index as defined in schema and what gets returned from SecondaryIndex#getIndexName(), which for the builtin index impls is the name of the underlying index CFS, of the form <base_table_name>.<index_name>.

This mismatch causes a number of UI inconsistencies:

nodetool rebuild_index <ks> <tbl> <idx>

<idx> must be qualified, i.e. include the redundant table name as without it, the rebuild silently fails

system.IndexInfo (which is also exposed over JMX) uses the form <tbl>.<idx>

cqlsh> describe index [<ks>.]<idx>

here, qualifying <idx> with the base table name is an error.

Generally, anything CQL related uses the index name directly, whereas anthing concerned with building or rebuiling requires the version based on an underlying backing table name.