Summary

DRIVERS-2761 added tests to ensure that search index management operations do not use read/write concerns, if they're provided to the driver search index management API.

But there are other scenarios where a read/write concern might be applied (they can be inherited from sessions). In Node, and possibly other drivers, read/write concern is applied in a different code path, depending on whether it was provided in an explicit session or as options to the operation. The tests added in DRIVERS-2761 only cover one of these codepaths, and as such Node still applies read/write concern to search index management commands if they should be inherited from a session (https://jira.mongodb.org/browse/NODE-6047).

Motivation

Who is the affected end user?

driver engineers.

How does this affect the end user?

Drivers may have bugs in their search index management helpers when they are used with sessions.

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

n/a

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

minor bug in the search index management API

Is this issue urgent?

no

Is this ticket required by a downstream team?

no

Is this ticket only for tests?

yes

Acceptance Criteria

What specific requirements must be met to consider the design phase complete?