[SERVER-70317] Do not append the read and write concern explicitly in _clusterQueryWithoutShardKey Created: 06/Oct/22 Updated: 29/Oct/23 Resolved: 10/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jason Zhang | Assignee: | Jason Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2022-10-17 |
| Participants: |
| Description |
|
Initially the command tests did not run the command within a transaction which had necessitated the explicit specification of read and write concerns. Having the command tests run within a transaction is more faithful to the expected usage of the command, which will automatically attach read and write concerns. |
| Comments |
| Comment by Githook User [ 10/Oct/22 ] |
|
Author: {'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}Message: |