Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-10127

Make naming for secondary indexes consistent

    XMLWordPrintableJSON

    Details

    • Severity:
      Normal

      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.

        Attachments

        1. 10127.txt
          17 kB
          Benjamin Lerer

          Activity

            People

            • Assignee:
              blerer Benjamin Lerer
              Reporter:
              samt Sam Tunnicliffe
              Authors:
              Benjamin Lerer
              Reviewers:
              T Jake Luciani
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: