Summary

Server added SERVER-37727: Enhance dropIndexes to accept multiple specific indexes to drop in 4.2, but this change wasn't propagated to all 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?

Users who want to drop multiple indexes with a single command.

How does this affect the end user?

The user wants to do in a Driver what they can already do with mongosh, and something that is implied by our documentation https://www.mongodb.com/docs/manual/reference/command/dropIndexes/ , specifically "To drop multiple indexes, specify an array of the index names."
They are annoyed/confused that functionality is missing in Node Driver (as well as other drivers), when that functionality is present in mongosh and is specifically called out in the documentation.

How likely is it that this problem or use case will occur?

This is one of the main paths in the usage of dropIndexes: delete all indexes, or delete a list of indexes. Node and other Drivers do not support specifying a list, forcing the user to make multiple dropIndex calls.

If the problem does occur, what are the consequences and how severe are they?

Performance concern and a requirement for the user to implement logic to perform this action.

Is this issue urgent?

No required timeline.

Is this ticket required by a downstream team?

Node Driver has a customer ticket, and that can only be resolved after this omission is added to the spec and subsequently to the Node Driver.

Is this ticket only for tests?

This has a functional impact, we need dropIndexes to accept an array of strings.

Acceptance Criteria

dropIndexes can accept a list of index names to drop.