-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Component/s: Index Management
-
None
-
Needed
Summary
What is the problem or use case, what are we trying to achieve?
Server added SERVER-37727: Enhance dropIndexes to accept multiple specific indexes to drop in 4.2, but this change wasn't propagated to the drivers or the specs.
It is present in mongosh, so this creates a confusing user experience, and a Node Driver user requested that this be fixed: NODE-7438: Add support for dropIndexes with multiple given indexes instead of all of them
Motivation
Who is the affected end user?
Who are the stakeholders?
How does this affect the end user?
Are they blocked? Are they annoyed? Are they confused?
How likely is it that this problem or use case will occur?
Main path? Edge case?
If the problem does occur, what are the consequences and how severe are they?
Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?
Is this issue urgent?
Does this ticket have a required timeline? What is it?
Is this ticket required by a downstream team?
Needed by e.g. Atlas, Shell, Compass?
Is this ticket only for tests?
Does this ticket have any functional impact, or is it just test improvements?
Acceptance Criteria
What specific requirements must be met to consider the design phase complete?
- related to
-
NODE-7438 Add support for dropIndexes with multiple given indexes instead of all of them
-
- Investigating
-
-
SERVER-37727 Enhance dropIndexes to accept multiple specific indexes to drop
-
- Closed
-