Managing Secondary Indexes

Describes how to manage secondary indexes, including adding, deleting, and listing indexes, setting up your cluster for querying, and troubleshooting index usage.

You can add and manage secondary indexes using either the maprcli table index commands or the MapR Control System (MCS). The maprcli table index commands are also available using the REST API. The following diagram provides links to information about managing indexes.

Describes the tasks needed to prepare your environment so you can query MapR-DB JSON tables using secondary indexes. Describes how to add secondary indexes on MapR-DB JSON tables. Describes how to view information about secondary indexes. This includes information about whether an index is lagging its parent JSON table. Describes how to use the MapR-DB shell to examine the contents of a secondary index. This includes displaying information about errors encountered inserting into the index. Describes how to verify that the data in a secondary index is consistent with its JSON table. This topic describes how to remove secondary indexes that are no longer needed. Describes how to debug and troubleshoot usage of secondary indexes.

The following permissions are required to add, remove, and list indexes. Indexes share the same volume and topology as its JSON table, so the applicable permissions are on the volume and JSON table path.

  • readAce on the volume
  • lookupdir on directories in the table path
Note: The mapr user is not treated as a superuser. MapR-DB does not allow the mapr user to perform this operation unless that user is given the relevant permission or permissions with access-control expressions.

Also, to add or remove an index, the user must be the creator of the table or a user with indexperm permission.