[SERVER-65444] Investigate planShardedSearch behavior if mongot sends an invalid/ill-formatted response Created: 11/Apr/22 Updated: 18/Apr/22 Resolved: 18/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ted Tuckman | Assignee: | Ted Tuckman |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | QO 2022-05-02 | ||||||||
| Participants: | |||||||||
| Description |
|
We observed in a test that the error when the mongotmock asserted during a command was misleading. We may be able to increase the clarity of these error messages |
| Comments |
| Comment by Ted Tuckman [ 18/Apr/22 ] |
|
This was addressed as part of |