mongosh doesn't behave like legacy shell with watch and maxAwaitTimeMS option

XMLWordPrintableJSON

    • Type: Investigation
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: 1.0.5
    • Component/s: Shell API
    • None
    • 2
    • None

      When using watch and the option maxAwaitTimeMS mongosh behaves differently than mongo legacy shell.

      db.resources.watch( [], { maxAwaitTimeMS: 20000 })

      Legacy shell will wait 20 seconds before returning back the cursor, while mongosh will return right after. Wondering if mongosh is not considering the option and then is using the default 1s maxAwaitTimeMS

            Assignee:
            Unassigned
            Reporter:
            Renato Riccio
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: