[DRIVERS-2761] Avoid Appending Write/Read Concern in Atlas Search Index Helper Commands Created: 02/Nov/23 Updated: 18/Jan/24 |
|
| Status: | Implementing |
| Project: | Drivers |
| Component/s: | Index Management |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Unknown |
| Reporter: | Slav Babanin | Assignee: | Kevin Albertson |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Changes: | Needed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Downstream Changes Summary: | Summary Confirm that write/read concern are not applied to Atlas Search Index Helper commands. This is the previously expected behavior, but was previously untested. If write/read concern are applied, omit them to avoid errors from Atlas. References New specification tests and prose tests are added in: https://github.com/mongodb/specifications/commit/0b47194538aa817978fae0f77f684f6d5e62ebab |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Engineering Lead: | |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Start date: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
SummaryIn the ticket Later, when some drivers had already implemented the spec, the specification was updated to reflect that write concern is not relevant. From the spec:
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
if write/read concern is included. This can lead to errors when users attempt to create Atlas Search Indexes. MotivationWho 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
|
| Comments |
| Comment by Githook User [ 12/Dec/23 ] |
|
Author: {'name': 'Kevin Albertson', 'email': 'kevin.albertson@mongodb.com', 'username': 'kevinAlbs'}Message: DRIVERS-2761 do not apply `readConcern` or `writeConcern` to search index commands (#1474)
--------- Co-authored-by: Jérôme Tamarelle <jerome@tamarelle.net> |