-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
Currently, calling dropIndex again with the same param after running it the first time, will result in an IndexNotFound error.
To repro:
assert.commandWorked(mongos.getCollection(ns).createIndex({x: 1}, {name: indexName, collation: {locale: "simple"}})); assert.commandWorked(mongos.getCollection(ns).dropIndex(indexName)); assert.commandWorked(mongos.getCollection(ns).dropIndex(indexName));
The second call to dropIndex() will fail with IndexNotFound
- depends on
-
SERVER-94982 Audit idempotency of all DDL operations
- Blocked
- is related to
-
SERVER-60064 Make create command idempotent on mongod
- Closed
-
SERVER-97226 dropIndexes command suppresses write concern errors.
- Closed
-
SERVER-43894 Make dropping a nonexistent collection a noop
- Closed
-
SERVER-94982 Audit idempotency of all DDL operations
- Blocked