Always capture non-enumerable _mongo property by the Multi-Router

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2026-03-16
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The _mongo property returned by query results is not captured in case of exhausted cursor.
      While this is usually correct, there are cases (like for some implicit transactions hooks) where the _mongo property is used to execute abort or commit on the same connection.
      This is automatically managed by the multi-router, so those commands must have a link against it so that it can redirect the commit against the pinned connection

            Assignee:
            Enrico Golfieri
            Reporter:
            Enrico Golfieri
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: