Docs Home → Develop Applications → MongoDB Manual
db.collection.createIndexes()![](/zh-cn/docs/v5.3/assets/link.svg)
Definition![](/zh-cn/docs/v5.3/assets/link.svg)
db.collection.createIndexes( [ keyPatterns ], options, commitQuorum )
Important
mongosh Method
This is a
mongosh
method. This is not the documentation forNode.js
or other programming language specific driver methods.In most cases,
mongosh
methods work the same way as the legacymongo
shell methods. However, some legacy methods are unavailable inmongosh
.For the legacy
mongo
shell documentation, refer to the documentation for the corresponding MongoDB Server release:For MongoDB API drivers, refer to the language specific MongoDB driver documentation.
Creates one or more indexes on a collection.
db.collection.createIndexes()
takes the following parameters:ParameterTypeDescriptionkeyPatterns
documentAn array containing index specification documents. Each document contains field and value pairs where the field is the index key and the value describes the type of index for that field. For an ascending index on a field, specify a value of
1
; for descending index, specify a value of-1
.MongoDB supports several different index types including text, geospatial, and hashed indexes. See index types for more information.
Changed in version 4.2: MongoDB 4.2 wildcard indexes support workloads where users query against custom fields or a large variety of fields in a collection:
To create a wildcard index on all fields and subfields in a document, specify
{ "$**" : 1 }
as the index key. You cannot specify a descending index key when creating a wildcard index.You can also either include or exclude specific fields and their subfields from the index using the optional
wildcardProjection
parameter.Wildcard indexes omit the
_id
field by default. To include the_id
field in the wildcard index, you must explicitly include it in thewildcardProjection
document:{ "wildcardProjection" : { "_id" : 1, "<field>" : 0|1 } } With the exception of explicitly including
_id
field, you cannot combine inclusion and exclusion statements in thewildcardProjection
document.You can create a wildcard index on a specific field and its subpaths by specifying the full path to that field as the index key and append
"$**"
to the path:{ "path.to.field.$**" : 1 }
You cannot specify a descending index key when creating a wildcard index.
The path-specific wildcard index syntax is incompatible with the
wildcardProjection
option. You cannot specify additional inclusions or exclusions on the specified path.
The wildcard index key must use one of the syntaxes listed above. For example, you cannot specify a compound index key. For more complete documentation on wildcard indexes, including restrictions on their creation, see Wildcard Index Restrictions.
The
mongod
featureCompatibilityVersion must be4.2
to create wildcard indexes. For instructions on setting the fCV, see Set Feature Compatibility Version on MongoDB 5.0 Deployments.For more information on creating wildcard indexes, see Wildcard Indexes.
options
documentOptional. A document that contains a set of options that controls the creation of the indexes. See Options for details.integer or stringOptional. The minimum number of data-bearing voting replica set members (i.e. commit quorum), including the primary, that must report a successful index build before the primary marks the
indexes
as ready. A "voting" member is any replica set member wheremembers[n].votes
is greater than0
.Supports the following values:
"votingMembers"
- all data-bearing voting replica set members (Default)."majority"
- a simple majority of data-bearing voting replica set members.<int>
- a specific number of data-bearing voting replica set members.0
- Disables quorum-voting behavior. Members start the index build simultaneously but do not vote or wait for quorum before completing the index build. If you start an index build with a commit quorum of0
, you cannot later modify the commit quorum usingsetIndexCommitQuorum
.A replica set tag name.
New in version 4.4.
The
db.collection.createIndexes()
is a wrapper around thecreateIndexes
command.To minimize the impact of building an index on replica sets and sharded clusters, use a rolling index build procedure as described on Rolling Index Builds on Replica Sets.
Options![](/zh-cn/docs/v5.3/assets/link.svg)
The options
document contains a set of options that control the
creation of the indexes. Different index types can have additional
options specific for that type.
Multiple index options can be specified in the same document. However,
if you specify multiple option documents the db.collection.createIndexes()
operation will fail.
Consider the following db.collection.createIndexes()
operation:
db.collection.createIndexes( [ { "a": 1 }, { "b": 1 } ], { unique: true, sparse: true, expireAfterSeconds: 3600 } )
If the options specification had been split into multiple documents
like this:
{ unique: true }, { sparse: true, expireAfterSeconds: 3600 }
the index creation operation would have failed.
Important
When you specify options to
db.collection.createIndexes()
, the options apply to
all of the specified indexes. For example, if you specify a
collation option, all of the created indexes will include that
collation.
db.collection.createIndexes()
will return an error if you
attempt to create indexes with incompatible options or too many
arguments. Refer to the option descriptions for more information.
Options for All Index Types![](/zh-cn/docs/v5.3/assets/link.svg)
The following options are available for all index types unless otherwise specified:
Parameter | Type | Description | |
---|---|---|---|
background | boolean | Optional. Deprecated in MongoDB 4.2.
| |
unique | boolean | Optional. Specifies that each index specified in the Specify The option is unavailable for hashed indexes. | |
name | string | Optional. The name of the index. If unspecified, MongoDB generates an index name by concatenating the names of the indexed fields and the sort order. NoteChanged in MongoDB 4.2Starting in version 4.2, for featureCompatibilityVersion set to Options specified to | |
partialFilterExpression | document | Optional. If specified, the indexes only reference documents that match the filter expression. See Partial Indexes for more information. A filter expression can include:
You can specify a | |
sparse | boolean | Optional. If The following index types are sparse by default and ignore this option: For a compound index that includes Changed in version 3.2: Starting in MongoDB 3.2, MongoDB provides the option to create partial indexes. Partial indexes offer a superset of the functionality of sparse indexes. If you are using MongoDB 3.2 or later, partial indexes should be preferred over sparse indexes. | |
expireAfterSeconds | integer | Optional. Specifies a value, in seconds, as a TTL to control how long
MongoDB retains documents in this collection. See
Expire Data from Collections by Setting TTL for more information on this
functionality. This applies only to TTL indexes. | |
boolean | Optional. A flag that determines whether the index is hidden from the query planner. A hidden index is not evaluated as part of the query plan selection. Default is To use the New in version 4.4. | ||
storageEngine | document | Optional. Allows users to configure the storage engine for the created indexes. The
Storage engine configuration options specified when creating indexes are validated and logged to the oplog during replication to support replica sets with members that use different storage engines. |
Option for Collation![](/zh-cn/docs/v5.3/assets/link.svg)
Parameter | Type | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
collation | document | Optional. Specifies the collation for the index. Collation allows users to specify language-specific rules for string comparison, such as rules for lettercase and accent marks. If you have specified a collation at the collection level, then:
The collation option has the following syntax:
When specifying collation, the |
The following indexes only support simple binary comparison and do not support collation:
text indexes,
2d indexes, and
geoHaystack indexes.
Tip
To create a text
, a 2d
, or a geoHaystack
index on a
collection that has a non-simple collation, you must explicitly
specify {collation: {locale: "simple"} }
when creating the
index.
Collation and Index Use![](/zh-cn/docs/v5.3/assets/link.svg)
If you have specified a collation at the collection level, then:
If you do not specify a collation when creating the index, MongoDB creates the index with the collection's default collation.
If you do specify a collation when creating the index, MongoDB creates the index with the specified collation.
Tip
By specifying a collation strength
of 1
or 2
, you can
create a case-insensitive index. Index with a collation strength
of 1
is both diacritic- and case-insensitive.
You can create multiple indexes on the same key(s) with different collations. To create indexes with the same key pattern but different collations, you must supply unique index names.
To use an index for string comparisons, an operation must also specify the same collation. That is, an index with a collation cannot support an operation that performs string comparisons on the indexed fields if the operation specifies a different collation.
For example, the collection myColl
has an index on a string
field category
with the collation locale "fr"
.
db.myColl.createIndex( { category: 1 }, { collation: { locale: "fr" } } )
The following query operation, which specifies the same collation as the index, can use the index:
db.myColl.find( { category: "cafe" } ).collation( { locale: "fr" } )
However, the following query operation, which by default uses the "simple" binary collator, cannot use the index:
db.myColl.find( { category: "cafe" } )
For a compound index where the index prefix keys are not strings, arrays, and embedded documents, an operation that specifies a different collation can still use the index to support comparisons on the index prefix keys.
For example, the collection myColl
has a compound index on the
numeric fields score
and price
and the string field
category
; the index is created with the collation locale
"fr"
for string comparisons:
db.myColl.createIndex( { score: 1, price: 1, category: 1 }, { collation: { locale: "fr" } } )
The following operations, which use "simple"
binary collation
for string comparisons, can use the index:
db.myColl.find( { score: 5 } ).sort( { price: 1 } ) db.myColl.find( { score: 5, price: { $gt: NumberDecimal( "10" ) } } ).sort( { price: 1 } )
The following operation, which uses "simple"
binary collation
for string comparisons on the indexed category
field, can use
the index to fulfill only the score: 5
portion of the query:
db.myColl.find( { score: 5, category: "cafe" } )
Options for text
Indexes![](/zh-cn/docs/v5.3/assets/link.svg)
The following options are available for text indexes only:
Parameter | Type | Description |
---|---|---|
weights | document | Optional. For text indexes, a document that contains
field and weight pairs. The weight is an integer ranging from 1 to
99,999 and denotes the significance of the field relative to the
other indexed fields in terms of the score. You can specify weights
for some or all the indexed fields. See
Control Search Results with Weights to adjust the scores.
The default value is Starting in MongoDB 5.0, the weights option is only allowed for text indexes. |
default_language | string | Optional. For text indexes, the language that
determines the list of stop words and the rules for the stemmer and
tokenizer. See Text Search Languages for the available
languages and Specify a Language for Text Index for
more information and examples. The default value is english . |
language_override | string | Optional. For text indexes, the name of the field, in
the collection's documents, that contains the override language for
the document. The default value is language . See
Use any Field to Specify the Language for a Document for an example. |
textIndexVersion | integer | Optional. The For available versions, see Versions. |
Options for 2dsphere
Indexes![](/zh-cn/docs/v5.3/assets/link.svg)
The following option is available for 2dsphere indexes only:
Parameter | Type | Description |
---|---|---|
2dsphereIndexVersion | integer | Optional. The For the available versions, see Versions. |
Options for 2d
Indexes![](/zh-cn/docs/v5.3/assets/link.svg)
The following options are available for 2d indexes only:
Options for geoHaystack
Indexes![](/zh-cn/docs/v5.3/assets/link.svg)
The following option is available for geoHaystack indexes only:
Parameter | Type | Description |
---|---|---|
bucketSize | number | For geoHaystack indexes, specify the number of units within which to group the location values; i.e. group in the same bucket those location values that are within the specified number of units to each other. The value must be greater than 0. |
Note
Removed in MongoDB 5.0
MongoDB 5.0 removes the deprecated geoHaystack index and geoSearch
command. Use a
2d index with $geoNear
or one of the
supported geospatial query operators
instead.
Upgrading your MongoDB instance to 5.0 and setting
featureCompatibilityVersion to 5.0
will delete any
pre-existing geoHaystack indexes.
Options for wildcard
indexes![](/zh-cn/docs/v5.3/assets/link.svg)
The following option is available for wildcard indexes only:
Parameter | Type | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
wildcardProjection | document | Optional. Allows users to include or exclude specific field paths from the wildcard index. This option is only valid if creating a wildcard index. The
The
Wildcard indexes omit the
With the exception of explicitly including Options specified to |
Behaviors![](/zh-cn/docs/v5.3/assets/link.svg)
Concurrency![](/zh-cn/docs/v5.3/assets/link.svg)
Changed in version 4.2.
For featureCompatibilityVersion "4.2"
, db.collection.createIndexes()
uses an optimized build process that obtains and holds an exclusive lock on
the specified collection at the start and end of the index build. All
subsequent operations on the collection must wait until db.collection.createIndexes()
releases
the exclusive lock. db.collection.createIndexes()
allows interleaving read and write
operations during the majority of the index build.
For featureCompatibilityVersion "4.0"
, db.collection.createIndexes()
uses the pre-4.2 index build process which by default obtains an exclusive
lock on the parent database for the entire duration of the build process. The
pre-4.2 build process blocks all operations on the database and all its
collections until the operation completed. background
indexes do not take
an exclusive lock.
For more information on the locking behavior of db.collection.createIndexes()
, see
Index Builds on Populated Collections.
Recreating an Existing Index![](/zh-cn/docs/v5.3/assets/link.svg)
If you call db.collection.createIndexes()
for an index or
indexes that already exist, MongoDB does not recreate the existing
index or indexes.
Index Options![](/zh-cn/docs/v5.3/assets/link.svg)
Non-Collation and Non-Hidden Options![](/zh-cn/docs/v5.3/assets/link.svg)
With the exception of the collation option, if you create an index with one set of index options and then try to recreate the same index but with different index options, MongoDB will not change the options nor recreate the index.
The hidden option can be changed without dropping and recreating the index. See Hidden Option.
To change the other index options, drop the existing index with
db.collection.dropIndex()
before running
db.collection.createIndexes()
with the new options.
Collation Option![](/zh-cn/docs/v5.3/assets/link.svg)
You can create multiple indexes on the same key(s) with different collations. To create indexes with the same key pattern but different collations, you must supply unique index names.
Hidden Option![](/zh-cn/docs/v5.3/assets/link.svg)
New in version 4.4.
Note
To hide an index, you must have featureCompatibilityVersion set to 4.4
or greater. However, once hidden, the
index remains hidden even with featureCompatibilityVersion set to 4.2
on MongoDB 4.4 binaries.
To hide or unhide existing indexes, you can use the following
mongosh
methods:
For example,
To change the
hidden
option for an index totrue
, use thedb.collection.hideIndex()
method:db.restaurants.hideIndex( { borough: 1, ratings: 1 } ); To change the
hidden
option for an index tofalse
, use thedb.collection.unhideIndex()
method:db.restaurants.unhideIndex( { borough: 1, city: 1 } );
Tip
See also:
Index Key Length Limit![](/zh-cn/docs/v5.3/assets/link.svg)
For MongoDB 2.6 through MongoDB versions with
featureCompatibilityVersion (fCV) set to "4.0"
or
earlier, MongoDB will not create an index on a collection if the
index entry for an existing document exceeds the Maximum Index Key Length.
Wildcard Indexes![](/zh-cn/docs/v5.3/assets/link.svg)
New in version 4.2.
Wildcard indexes omit the
_id
field by default. To include the_id
field in the wildcard index, you must explicitly include it in thewildcardProjection
document:{ "wildcardProjection" : { "_id" : 1, "<field>" : 0|1 } } With the exception of explicitly including
_id
field, you cannot combine inclusion and exclusion statements in thewildcardProjection
document.The
mongod
featureCompatibilityVersion must be4.2
to create wildcard indexes. For instructions on setting the fCV, see Set Feature Compatibility Version on MongoDB 5.0 Deployments.Wildcard indexes do not support the following index types or properties:
Note
Wildcard Indexes are distinct from and incompatible with Wildcard Text Indexes. Wildcard indexes cannot support queries using the
$text
operator.For complete documentation on wildcard index restrictions, see Wildcard Index Restrictions.
For examples of wildcard index creation, see Create a Wildcard Index. For complete documentation on Wildcard Indexes, see Wildcard Indexes.
Transactions![](/zh-cn/docs/v5.3/assets/link.svg)
Changed in version 4.4.
Starting in MongoDB 4.4, you can create collections and indexes inside a multi-document transaction if the transaction is not a cross-shard write transaction.
To use db.collection.createIndexes()
in a transaction, the transaction must use read
concern "local"
. If you specify a read concern level
other than "local"
, the transaction fails.
Tip
Example![](/zh-cn/docs/v5.3/assets/link.svg)
Tip
See also:
db.collection.createIndex()
for examples of various index
specifications.
Create Indexes Without Options![](/zh-cn/docs/v5.3/assets/link.svg)
Consider a restaurants
collection containing documents that
resemble the following:
{ location: { type: "Point", coordinates: [-73.856077, 40.848447] }, name: "Morris Park Bake Shop", cuisine: "Cafe", borough: "Bronx", }
The following example creates two indexes on the restaurants
collection: an ascending index on the borough
field and a
2dsphere index on the location
field.
db.restaurants.createIndexes([{"borough": 1}, {"location": "2dsphere"}])
Create Indexes with Collation Specified![](/zh-cn/docs/v5.3/assets/link.svg)
The following example creates two indexes on the products
collection: an ascending index on the manufacturer
field and an
ascending index on the category
field. Both indexes use a collation that specifies the locale fr
and
comparison strength 2
:
db.products.createIndexes( [ { "manufacturer": 1}, { "category": 1 } ], { collation: { locale: "fr", strength: 2 } })
For queries or sort operations on the indexed keys that uses the same collation rules, MongoDB can use the index. For details, see Collation and Index Use.
Create a Wildcard Index![](/zh-cn/docs/v5.3/assets/link.svg)
New in version 4.2: The mongod
featureCompatibilityVersion must be 4.2
to
create wildcard indexes. For instructions on setting the fCV, see
Set Feature Compatibility Version on MongoDB 5.0 Deployments.
For complete documentation on Wildcard Indexes, see Wildcard Indexes.
The following lists examples of wildcard index creation:
Create a Wildcard Index on a Single Field Path![](/zh-cn/docs/v5.3/assets/link.svg)
Consider a collection products_catalog
where documents may contain a
product_attributes
field. The product_attributes
field can
contain arbitrary nested fields, including embedded
documents and arrays:
{ "_id" : ObjectId("5c1d358bf383fbee028aea0b"), "product_name" : "Blaster Gauntlet", "product_attributes" : { "price" : { "cost" : 299.99 "currency" : USD } ... } }, { "_id" : ObjectId("5c1d358bf383fbee028aea0c"), "product_name" : "Super Suit", "product_attributes" : { "superFlight" : true, "resistance" : [ "Bludgeoning", "Piercing", "Slashing" ] ... }, }
The following operation creates a wildcard index on the
product_attributes
field:
use inventory db.products_catalog.createIndexes( [ { "product_attributes.$**" : 1 } ] )
With this wildcard index, MongoDB indexes all scalar values of
product_attributes
. If the field is a nested document or array, the
wildcard index recurses into the document/array and indexes all scalar
fields in the document/array.
The wildcard index can support arbitrary single-field queries on
product_attributes
or one of its nested fields:
db.products_catalog.find( { "product_attributes.superFlight" : true } ) db.products_catalog.find( { "product_attributes.maxSpeed" : { $gt : 20 } } ) db.products_catalog.find( { "product_attributes.elements" : { $eq: "water" } } )
Note
The path-specific wildcard index syntax is incompatible with the
wildcardProjection
option. See the parameter documentation for more
information.
Create a Wildcard Index on All Field Paths![](/zh-cn/docs/v5.3/assets/link.svg)
Consider a collection products_catalog
where documents may contain a
product_attributes
field. The product_attributes
field can
contain arbitrary nested fields, including embedded
documents and arrays:
{ "_id" : ObjectId("5c1d358bf383fbee028aea0b"), "product_name" : "Blaster Gauntlet", "product_attributes" : { "price" : { "cost" : 299.99 "currency" : USD } ... } }, { "_id" : ObjectId("5c1d358bf383fbee028aea0c"), "product_name" : "Super Suit", "product_attributes" : { "superFlight" : true, "resistance" : [ "Bludgeoning", "Piercing", "Slashing" ] ... }, }
The following operation creates a wildcard index on all scalar fields
(excluding the _id
field):
use inventory db.products_catalog.createIndexes( [ { "$**" : 1 } ] )
With this wildcard index, MongoDB indexes all scalar fields for each document in the collection. If a given field is a nested document or array, the wildcard index recurses into the document/array and indexes all scalar fields in the document/array.
The created index can support queries on any arbitrary field within documents in the collection:
db.products_catalog.find( { "product_price" : { $lt : 25 } } ) db.products_catalog.find( { "product_attributes.elements" : { $eq: "water" } } )
Note
Wildcard indexes omit the _id
field by default. To include the
_id
field in the wildcard index, you must explicitly include it
in the wildcardProjection
document. See parameter documentation for
more information.
Create a Wildcard Index on Multiple Specific Field Paths![](/zh-cn/docs/v5.3/assets/link.svg)
Consider a collection products_catalog
where documents may contain a
product_attributes
field. The product_attributes
field can
contain arbitrary nested fields, including embedded
documents and arrays:
{ "_id" : ObjectId("5c1d358bf383fbee028aea0b"), "product_name" : "Blaster Gauntlet", "product_attributes" : { "price" : { "cost" : 299.99 "currency" : USD } ... } }, { "_id" : ObjectId("5c1d358bf383fbee028aea0c"), "product_name" : "Super Suit", "product_attributes" : { "superFlight" : true, "resistance" : [ "Bludgeoning", "Piercing", "Slashing" ] ... }, }
The following operation creates a wildcard index and uses
the wildcardProjection
option to include only scalar values of the
product_attributes.elements
and product_attributes.resistance
fields in the index.
use inventory db.products_catalog.createIndexes( [ { "$**" : 1 } ], { "wildcardProjection" : { "product_attributes.elements" : 1, "product_attributes.resistance" : 1 } } )
While the key pattern "$**"
covers all fields in the document, the
wildcardProjection
field limits the index to only the included
fields. For complete documentation on wildcardProjection
, see
Options for wildcard
indexes.
If a field is a nested document or array, the wildcard index recurses into the document/array and indexes all scalar fields in the document/array.
The created index can support queries on any scalar field
included in the wildcardProjection
:
db.products_catalog.find( { "product_attributes.elements" : { $eq: "Water" } } ) db.products_catalog.find( { "product_attributes.resistance" : "Bludgeoning" } )
Note
Wildcard indexes do not support mixing inclusion and exclusion
statements in the wildcardProjection
document except when
explicitly including the _id
field. For more information on
wildcardProjection
, see the parameter documentation.
Create a Wildcard Index that Excludes Multiple Specific Field Paths![](/zh-cn/docs/v5.3/assets/link.svg)
Consider a collection products_catalog
where documents may contain a
product_attributes
field. The product_attributes
field can
contain arbitrary nested fields, including embedded
documents and arrays:
{ "_id" : ObjectId("5c1d358bf383fbee028aea0b"), "product_name" : "Blaster Gauntlet", "product_attributes" : { "price" : { "cost" : 299.99 "currency" : USD } ... } }, { "_id" : ObjectId("5c1d358bf383fbee028aea0c"), "product_name" : "Super Suit", "product_attributes" : { "superFlight" : true, "resistance" : [ "Bludgeoning", "Piercing", "Slashing" ] ... }, }
The following operation creates a wildcard index and uses
the wildcardProjection
document to index all scalar fields
for each document in the collection, excluding the
product_attributes.elements
and product_attributes.resistance
fields:
use inventory db.products_catalog.createIndexes( [ { "$**" : 1 } ], { "wildcardProjection" : { "product_attributes.elements" : 0, "product_attributes.resistance" : 0 } } )
While the key pattern "$**"
covers all fields in the document, the
wildcardProjection
field excludes the specified fields from the
index. For complete documentation on wildcardProjection
, see
Options for wildcard
indexes.
If a field is a nested document or array, the wildcard index recurses into the document/array and indexes all scalar fields in the document/array.
The created index can support queries on any scalar field except
those excluded by wildcardProjection
:
db.products_catalog.find( { "product_attributes.maxSpeed" : { $gt: 25 } } ) db.products_catalog.find( { "product_attributes.superStrength" : true } )
Note
Wildcard indexes do not support mixing inclusion and exclusion
statements in the wildcardProjection
document except when
explicitly including the _id
field. For more information on
wildcardProjection
, see the parameter documentation.
Create Indexes With Commit Quorum![](/zh-cn/docs/v5.3/assets/link.svg)
Note
Requires featureCompatibilityVersion 4.4+
Each mongod
in the replica set or sharded cluster
must have featureCompatibilityVersion set to at
least 4.4
to start index builds simultaneously across
replica set members.
MongoDB 4.4 running featureCompatibilityVersion: "4.2"
builds
indexes on the primary before replicating the index build to
secondaries.
Starting with MongoDB 4.4, index builds on a replica set or sharded
cluster build simultaneously across all data-bearing replica set
members. For sharded clusters, the index build occurs only on shards
containing data for the collection being indexed. The primary
requires a minimum number of data-bearing voting
members (i.e commit quorum), including itself,
that must complete the build before marking the index as ready for
use. See Index Builds in Replicated Environments for more
information.
Specify the commitQuorum
parameter to the createIndexes()
operation to set
the minimum number of data-bearing voting members (i.e commit
quorum), including the primary, which must complete the index build
before the primary marks the indexes as ready. The default commit quorum
is votingMembers
, or all data-bearing voting replica set members.
The following operation creates an index with a commit quorum of "majority"
:
db.getSiblingDB("examples").invoices.createIndexes( { "invoices" : 1 }, { }, "majority" )
The primary marks index build as ready only after a simple majority of data-bearing voting members "vote" to commit the index build. For more information on index builds and the voting process, see Index Builds in Replicated Environments.
Create Multiple Indexes![](/zh-cn/docs/v5.3/assets/link.svg)
Create a cakeSales
collection that contains cake sales in the states
of California (CA
) and Washington (WA
):
db.cakeSales.insertMany( [ { _id: 0, type: "chocolate", orderDate: new Date("2020-05-18T14:10:30Z"), state: "CA", price: 13, quantity: 120 }, { _id: 1, type: "chocolate", orderDate: new Date("2021-03-20T11:30:05Z"), state: "WA", price: 14, quantity: 140 }, { _id: 2, type: "vanilla", orderDate: new Date("2021-01-11T06:31:15Z"), state: "CA", price: 12, quantity: 145 }, { _id: 3, type: "vanilla", orderDate: new Date("2020-02-08T13:13:23Z"), state: "WA", price: 13, quantity: 104 }, { _id: 4, type: "strawberry", orderDate: new Date("2019-05-18T16:09:01Z"), state: "CA", price: 41, quantity: 162 }, { _id: 5, type: "strawberry", orderDate: new Date("2019-01-08T06:12:03Z"), state: "WA", price: 43, quantity: 134 } ] )
The following example creates multiple indexes on the cakeSales
collection:
db.cakeSales.createIndexes( [ { "type": 1 }, { "orderDate": 1 }, { "state": 1 }, { "orderDate": 1, "state": -1 } ] )
The first three indexes are on single fields and in ascending order
(1
).
The last index is on orderDate
in ascending order (1
) and
state
in descending order (-1
).
Additional Information![](/zh-cn/docs/v5.3/assets/link.svg)
For additional information about indexes, refer to:
The Indexes section of this manual for full documentation of indexes and indexing in MongoDB.
db.collection.getIndexes()
to view the specifications of existing indexes for a collection.Text Indexes for details on creating
text
indexes.Geospatial Indexes for geospatial queries.
TTL Indexes for expiration of data.