On this page本页内容
db.collection.dropIndex(index)
This is a mongosh
method. This is not the documentation for Node.js
or other programming language specific driver methods.
In most cases, mongosh
methods work the same way as the legacy mongo
shell methods. However, some legacy methods are unavailable in mongosh
.
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.
Drops or removes the specified index from a collection. 从集合中删除或移除指定的索引。The db.collection.dropIndex()
method provides a wrapper around the dropIndexes
command.db.collection.dropIndex()
方法提供了dropIndexes
命令的包装。
_id
field._id
字段上的默认索引。db.collection.dropIndex("*")
to drop all non-_id
indexes. db.collection.dropIndex("*")
来删除所有非_id
索引。db.collection.dropIndexes()
instead.db.collection.dropIndexes()
。The db.collection.dropIndex()
method takes the following parameter:db.collection.dropIndex()
方法采用以下参数:
index | string or document |
|
To get the index name or the index specification document for the 要获取db.collection.dropIndex()
method, use the db.collection.getIndexes()
method.db.collection.dropIndex()
方法的索引名称或索引规范文档,请使用db.collection.getIndexes()
方法。
Starting in MongoDB 5.2, you can use 从MongoDB 5.2开始,您可以使用db.collection.dropIndex()
to drop existing indexes on the same collection even if there is a build in progress on another index. db.collection.dropIndex()
删除同一集合上的现有索引,即使另一个索引上正在进行构建。In earlier versions, attempting to drop a different index during an in-progress index build results in a 在早期版本中,在进行索引生成期间尝试删除其他索引会导致BackgroundOperationInProgressForNamespace
error.BackgroundOperationInProgressForNamespace
错误。
Changed in version 4.2.在版本4.2中更改。
db.collection.dropIndex()
obtains an exclusive lock on the specified collection for the duration of the operation. 在操作期间获取指定集合的独占锁。All subsequent operations on the collection must wait until 集合上的所有后续操作必须等待db.collection.dropIndex()
releases the lock.db.collection.dropIndex()
释放锁。
Prior to MongoDB 4.2, 在MongoDB 4.2之前,db.collection.dropIndex()
obtained an exclusive lock on the parent database, blocking all operations on the database and all its collections until the operation completed.db.collection.dropIndex()
获得了父数据库的独占锁,阻止了数据库及其所有集合上的所有操作,直到操作完成。
Starting in MongoDB 4.4, if an index specified to 从MongoDB 4.4开始,如果指定给db.collection.dropIndex()
is still building, db.collection.dropIndex()
attempts to stop the in-progress build. db.collection.dropIndex()
的索引仍在构建中,db.collection.dropIndex()
会尝试停止正在进行的构建。Stopping an index build has the same effect as dropping the built index. 停止索引生成与删除生成的索引具有相同的效果。In versions earlier than MongoDB 4.4, 在MongoDB 4.4之前的版本中,如果集合上正在进行任何索引构建,db.collection.dropIndex()
returns an error if there are any index builds in progress on the collection.db.collection.dropIndex()
将返回错误。
For replica sets, run 对于副本集,请在db.collection.dropIndex()
on the primary. primary
上运行db.collection.dropIndex()
。The primary stops the index build and creates an associated "abortIndexBuild" oplog entry. primary
停止索引构建并创建关联的“abortIndexBuild”oplog条目。Secondaries which replicate the "abortIndexBuild" oplog entry stop the in-progress index build and discard the build job. 复制“abortIndexBuild”oplog条目的秒停止正在进行的索引构建并放弃构建作业。See Index Build Process for detailed documentation on the index build process.有关索引生成过程的详细文档,请参阅索引生成过程。
Use 使用currentOp
to identify the index builds associated with a createIndexes
or db.collection.createIndexes()
operation. currentOp
标识与createIndexes
或db.collection.createIndexes()
操作关联的索引构建。See Active Indexing Operations for an example.有关示例,请参阅活动索引操作。
Starting in version 4.4, MongoDB adds the ability to hide or unhide indexes from the query planner. 从4.4版开始,MongoDB添加了在查询计划程序中隐藏或取消隐藏索引的功能。By hiding an index from the planner, users can evaluate the potential impact of dropping an index without actually dropping the index.通过向计划者隐藏索引,用户可以评估删除索引的潜在影响,而无需实际删除索引。
If after the evaluation, the user decides to drop the index, the user can drop the hidden index; i.e. you do not need to unhide it first to drop it.如果在评估后,用户决定删除索引,则用户可以删除隐藏的索引;也就是说,您不需要先取消隐藏它就可以放下它。
If, however, the impact is negative, the user can unhide the index instead of having to recreate a dropped index. 但是,如果影响是负面的,用户可以取消隐藏索引,而不必重新创建删除的索引。And because indexes are fully maintained while hidden, the indexes are immediately available for use once unhidden.由于索引在隐藏时得到了完全维护,因此一旦取消隐藏,索引就可以立即使用。
For more information on hidden indexes, see Hidden Indexes.有关隐藏索引的详细信息,请参阅隐藏索引。
Consider a 考虑集合pets
collection. pets
。Calling the 对db.collection.getIndexes()
method on the pets
collection returns the following indexes:pets
集合调用db.collection.getIndexes()
方法将返回以下索引:
[ { "v" : 2, "key" : { "_id" : 1 }, "name" : "_id_" }, { "v" : 2, "key" : { "cat" : -1 }, "name" : "catIdx" }, { "v" : 2, "key" : { "cat" : 1, "dog" : -1 }, "name" : "cat_1_dog_-1" } ]
The single field index on the field 字段cat
has the user-specified name of catIdx
[1] and the index specification document of { "cat" : -1 }
.cat
上的单个字段索引具有用户指定的名称catIdx
[1]和索引规范文档{ "cat" : -1 }
。
To drop the index 要删除索引catIdx
, you can use either the index name:catIdx
,可以使用索引名称:
db.pets.dropIndex( "catIdx" )
Or you can use the index specification document 或者可以使用索引规范文档{ "cat" : -1 }
:{ "cat" : -1 }
:
db.pets.dropIndex( { "cat" : -1 } )
[1] | cat_1 .cat_1 。 |