-
Type:
New Feature
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Index Maintenance, Querying
-
Query
-
Fully Compatible
-
v4.4
-
Query 2018-03-12, Query 2018-03-26, Execution Team 2020-03-09, Execution Team 2020-03-23
-
(copied to CRM)
-
88
It would be helpful if there was a way to disable an index before dropping. Been clearing out some unused production indexes lately, but there's always a tense moment after issuing the dropIndex command where I wait to see if it was less "unused" than expected.
If there was a way to just disable the index (semantics would be that it keeps getting updated, just can't be used by queries), then a revert would be much faster if something goes wrong and the drop could be done with more confidence.
- causes
-
SERVER-47846 CollMod (_collModInternal) unsafely accesses an IndexCatalogEntry that is destructed in an onRollback handler
-
- Closed
-
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
SERVER-26589 make the mongodb support invisible index
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- related to
-
SERVER-47275 Take over and complete Hidden Indexes PR
-
- Closed
-
-
-
- Closed
-
- links to