Summary

In the ticket DRIVERS-2637, Atlas Search Index helper methods were introduced.

Later, when some drivers had already implemented the spec, the specification was updated to reflect that write concern is not relevant. From the spec:

These commands internally proxy the search index management commands to a separate process that runs alongside an Atlas cluster. As such, read concern and write concern are not relevant for the search index management commands.

However, some of the drivers might still append write or read concerns to the commands.

Currently, the existing prose tests don't have a specific case to ensure that write/read concerns are not included in the index search commands. This means that some drivers may not be aware that the server will produce an error 

(InvalidOptions) with the message 'Command does not support writeConcern'

 if write/read concern is included. This can lead to errors when users attempt to create Atlas Search Indexes.

Motivation

Who is the affected end user?

The affected end user is any developer or administrator using MongoDB drivers to interact with Atlas Search.

How does this affect the end user?

This affects the end users by potentially causing errors during the creation of Atlas Search Indexes if write/read concerns are inadvertently appended to the commands. Users might be confused or annoyed by these errors.

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

The likelihood of this problem occurring is moderate.

Is this issue urgent?

This issue is moderately urgent as it can lead to errors for users trying to create Atlas Search Indexes.

Is this ticket only for tests?

This ticket primarily addresses a functional improvement by ensuring that write/read concerns are not appended to Atlas Search Index helper commands. 

Acceptance Criteria

1. When executing Atlas Search Index helper commands, write/read concern must not be appended.

1. Add a test case to verify that write/read concerns are not appended to Atlas Search Index commands.