Navigation

Manage Indexes in Data Explorer

You can use the Data Explorer to manage indexes on your collections.

Indexes support the efficient execution of queries in MongoDB and should be considered for fields which your application reads often. To learn more about creating effective indexes, see Indexing Strategies.

To access the Data Explorer:

  1. Click Clusters in the top-left corner of Atlas.
  2. Click Collections for your desired cluster.

Or, if you are already viewing a specific cluster, select the Collections tab.

To create or drop indexes, you must have access provided by at least one of the following roles:

From the Collections tab, you can view index information for a collection. To view index information for a collection:

1

The main panel and Namespaces on the left side list the collections in the database.

Screenshot highlighting databases in Data Explorer.
2

The main panel displays the Find, Indexes, and Aggregation views.

3

The indexes table lists the indexes and associated index information for the collection. Index information includes the index definition, the size, and the usage frequency.

Screenshot highlighting index view in Data Explorer.
Tip

When you create indexes, keep the ratio of reads to writes on the target collection in mind. Indexes come with a performance cost, but are more than worth the cost for frequent queries on large data sets. To learn more about indexing strategies, see Indexing Strategies.

To create an index for a collection through the Data Explorer:

1

Select the collection you wish to index, and go to the Indexes tab.

2

In the Create Index modal, enter the index key specification document:

{ <field1>: <index type>, ... }
Example

To create a compound index on the fields category (ascending order) and score (descending order), specify the index specification document:

{ category: 1, score: -1 }

For more information on indexes, see Indexes.

3
{ <option1>: <value1>, ... }
Example

The following options document specifies the unique option and the name for the index:

{ unique: true, name: "myUniqueIndex" }
Note

You cannot perform a rolling build for a unique index. If you enable building indexes in a rolling fashion with the unique index option, Atlas rejects your configuration with an error message.

4

Use collation to specify language-specific rules for string comparison, such as rules for lettercase and accent marks. The collation document contains a locale field which indicates the ICU Locale code, and may contain other fields to define collation behavior.

Example

The following collation option document specifies a locale value of fr for a French language collation:

{ "locale": "fr" }

To review the list of locales that MongoDB collation supports, see the list of languages and locales. To learn more about collation options, including which are enabled by default for each locale, see Collation in the MongoDB manual.

5
Note

Data Explorer does not support building indexes with a rolling build for M0 Free Tier and M2/M5 shared clusters.

Building indexes in a rolling fashion reduces the performance impact of building indexes on replica sets and sharded clusters.

To maintain cluster availability:

  • Atlas removes one node from the cluster at a time starting with a secondary.
  • More than one node can go down at a time, but Atlas always keeps a majority of the nodes online.

To learn more about rebuilding indexes, see Build Indexes on Replica Sets.

Note

The following index options are incompatible with building indexes in a rolling fashion:

If you specify any of these options in the Options pane, Atlas rejects your configuration with an error message.

6
7

To drop an index from a collection through the Data Explorer:

1

Select the collection whose index you wish to drop, and go to the Indexes tab.

2
3

Confirm by typing the name of the index, and click Drop.

Note

You cannot delete the _id index.

Give Feedback