When the server kills an idle cursor, reading from that cursor on the client doesn't produce an error

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.0, 1.4.12
    • Affects Version/s: None
    • Component/s: None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This makes it impossible to know if your cursor has ended because you've read all the data or if it has ended because it timed out on the server, without first doing a count query and making sure that you get the same number of documents.

      See: https://github.com/mongodb/node-mongodb-native/blob/master/test/tests/manual_tests/cursor_timeout_test.js

            Assignee:
            Christian Amor Kvalheim
            Reporter:
            Alex Zylman
            None
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: