[GODRIVER-1934] Correct cursor options are not always passed down to the operations layer Created: 25/Mar/21 Updated: 28/Oct/23 Resolved: 16/Apr/21 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.5.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Divjot Arora (Inactive) | Assignee: | Divjot Arora (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
One example: Database#ListCollections does not set CursorOptions.CommandMonitor, so getMore/killCursors operations on the resulting cursor will not result in published events. We should ensure there are tests for every cursor-creating operation to force multiple batches and assert that all commands are published. |
| Comments |
| Comment by Githook User [ 16/Apr/21 ] |
|
Author: {'name': 'Divjot Arora', 'email': 'divjot.arora@10gen.com', 'username': 'divjotarora'}Message: |
| Comment by Divjot Arora (Inactive) [ 05/Apr/21 ] |
|
PR for the backport to release/1.5: https://github.com/mongodb/mongo-go-driver/pull/630 |
| Comment by Githook User [ 05/Apr/21 ] |
|
Author: {'name': 'Divjot Arora', 'email': 'divjot.arora@10gen.com', 'username': 'divjotarora'}Message: |
| Comment by Divjot Arora (Inactive) [ 29/Mar/21 ] |