Sam Tunnicliffe created CASSANDRA-10127:
-------------------------------------------
Summary: Make naming for secondary indexes consistent
Key: CASSANDRA-10127
URL: https://issues.apache.org/jira/browse/CASSANDRA-10127
Project: Cassandra
Issue Type: Bug
Reporter: Sam Tunnicliffe
Assignee: Sam Tunnicliffe
Fix For: 3.0 beta 2
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:
{code}nodetool rebuild_index <ks> <tbl> <idx>{code}
{{<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>}}
{code}cqlsh> describe index [<ks>.]<idx>{code}
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
