[GODRIVER-387] Initial aggregate command for a change stream should not be retried Created: 25/Apr/18 Updated: 27/Oct/23 Resolved: 06/May/18 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Rathi Gnanasekaran | Assignee: | Unassigned |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Epic Link: | GODRIVER MongoDB 4.0 Support | ||||||||
| Description |
|
If any driver has implemented retry on the initial aggregate command, they will need to ensure that aggregate commands are not retried. |
| Comments |
| Comment by Jeffrey Yemin [ 06/May/18 ] |
|
Confirmed that the change stream implementation does not retry the aggregate command |