[SERVER-70894] Add an overload for async_rpc::sendCommand that doesn't require a targeter Created: 27/Oct/22 Updated: 29/Oct/23 Resolved: 10/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | George Wangensteen | Assignee: | Alex Li |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Service Arch 2022-12-26, Service Arch 2023-01-09, Service Arch 2023-01-23, Service Arch 2023-02-06, Service Arch 2023-02-20 |
| Participants: |
| Description |
|
matt.broadstone@mongodb.com points out that the advanced functionality of a Targeter is often not needed when sending an RPC request, because a default of ReadPreference "primary" is almost always what users want. In such cases, a URI (or even shard ID) is sufficient to target the RPC request. Let's add and document an overload that takes a URI and/or shardID instead of a Targeter, so that users don't need to manage additional state/complexity in the "easy" case. |
| Comments |
| Comment by Githook User [ 07/Feb/23 ] |
|
Author: {'name': 'Alex Li', 'email': 'alex.li@mongodb.com', 'username': 'lia394126'}Message: |