[JAVA-3871] Change stream resumption does not always include resumeAfter Created: 26/Oct/20 Updated: 28/Oct/23 Resolved: 20/Jan/21 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Change Streams |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.0, 3.12.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
The Test consecutive resume test from the unified test file format specification uncovers a bug in the Java driver. The test expects that after a failed getMore, the subsequent aggregate command includes the resumeAfter field populated with the postBatchResumeToken from the initial aggregate command. The Java driver fails this test. The bug seems to only happen in situations where the initiating aggregate command contains no results and the first getMore command fails. |
| Comments |
| Comment by Githook User [ 20/Jan/21 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Ensure that resumeToken is included on resume attempts (#634)
|