Indexes are special data structures that improve query performance. Indexes store a portion of a collection's data in an easy-to-traverse form. The index stores the value of a specific field or set of fields, ordered by the value of the field.
To improve query performance, build indexes on fields that appear often in queries and for all operations that sort by a field.
Queries on an indexed field can use the index to limit the number of documents that must be scanned to find matching documents.
Sort operations on an indexed field can return documents pre-sorted by the index.
To learn more about indexes, see Indexes.
Indexes have some negative performance impact on write operations. For collections with high write-to-read ratio, indexes are expensive since each insert must also update any indexes. For a detailed list of considerations for indexes, see Operational Considerations for Indexes.
The Indexes tab lists the existing indexes for a collection.
To access the Indexes tab for a collection, click on the collection on the left hand pane and select the Indexes tab.
For each index, Compass displays the following information:
Name and Definition
The name of the index and keys.
Regular, text, geospatial or hashed index.
How large the index is.
Number of times the index has been used in a lookup since the time the index was created or the last server restart.
Any special properties (such as uniqueness, partial) of the index.
From the Indexes tab, click the Create Index button.
Specify an index key.
To specify an existing document field as an index key, select the field from the dropdown list.
To specify a field that does not exist in any document as an index key, enter the field name in the input box.
To create a compound index, click the icon next to the index type dropdown.
Use the dropdown to the right of each field name to specify the index type. You can specify one of the following types:
To learn how to specify a wildcard index, see Create a Wildcard Index.
Compass supports the following index options:
Create unique index
Ensure that the indexed fields do not store duplicate values.
Specify a name for the index.
Create a TTL index
Delete documents automatically after a specified number of seconds since the indexed field value.
Partial filter expression
Index only the documents which match the specified filter expression.
The following partial filter expression only indexes
documents where the
Use custom collation
Create a custom collation for the index using the options provided in Compass.
Wildcard projection (New in MongoDB 4.2)
Support unknown or arbitrary fields which match the specified
projection in the index. To use a wildcard projection, set
your index field name to
Consider the following wildcard projection document:
If your index field name is
To create an Atlas Search index, see Create an Atlas Search Index.
New in version v4.2.
You can create wildcard indexes to
support queries against unknown or arbitrary fields. To create a
wildcard index in Compass, manually type the wildcard index
<field>.$**) into the Select a field name
Consider a collection where documents contain a
object. The fields within the
userMetadata object may vary
You can create a wildcard index on
userMetadata to account for
all potential fields within the object. Type the following into
the Select a field name input:
Specify a type (
descending) for your wildcard
index, then click Create Index.
Compass shows the type of your new index as Wildcard.
You can hide an index from the query planner to evaluate the potential impact of dropping an index without actually dropping the index.
From the Indexes tab, to delete an index, click on the trash can icon for that index. A confirmation dialog appears.
Creating, hiding, and dropping indexes is not permitted in MongoDB Compass Readonly Edition.
The Indexes tab is not available if you are connected to a Data Lake.