Correct cursor options are not always passed down to the operations layer

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 1.5.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Divjot Arora (Inactive)
            Reporter:
            Divjot Arora (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: