[GODRIVER-2605] Error if MaxAwaitTime will cause client-side timeout Created: 24/Oct/22 Updated: 18/Jan/24 Resolved: 18/Jan/24 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Benji Rewis (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Stabilize CSOT |
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
| Description |
|
When users set MaxAwaitTime and Timeout , getMore s from change streams or cursors can currently append multiple maxTimeMS values. Remove maxTimeMS appension logic in batch cursor. Modify calculateMaxTimeMS to respect MaxTime for getMore unless Timeout is set and deadline will be exceeded. If deadline will be exceeded, throw ErrDeadlineWouldBeExceeded with relevant information. |