ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Observability
    • Hide

      DRIVERS-3598:
      Summary of necessary driver changes

      • Update the unified test runner to support schema 1.29. It adds the $$gte operator and applies ignoreExtraSpans at every level of the span tree. A runner capped at 1.28 rejects the new fixtures before matching begins:
        db.mongodb.cursor_id: { $$gte: 1 }
        
      • Give each user-initiated getMore its own operation span, sibling to the cursor-creating operation's span. Driver-internal iteration adds no operation spans, no span is scoped to a cursor's lifetime, and a change stream resume ends the failed span while giving killCursors none.
      • Drivers now MUST set db.mongodb.cursor_id on operation spans that create a cursor or operate on a single existing cursor. It is never a literal 0, and for a getMore it holds the id the driver sent rather than the 0 the reply may return.
      • Add spec tests from https://github.com/mongodb/specifications/commit/d1ac31b730d87c6cc18d126149da30008ef12561 and implement prose tests 3 and 4.

      Commits for syncing spec/prose tests

      Context for other referenced/linked tickets

      • DRIVERS-3627 tracks optional span links between the sibling getMore and cursor-creating operation spans.
      • DRIVERS-3626 fixed MongoDB 4.2 server orchestration. Earlier patch runs for this ticket show two unrelated failures.
      Show
      DRIVERS-3598 : Summary of necessary driver changes Update the unified test runner to support schema 1.29. It adds the $$gte operator and applies ignoreExtraSpans at every level of the span tree. A runner capped at 1.28 rejects the new fixtures before matching begins: db.mongodb.cursor_ id: { $$ gte: 1 } Give each user-initiated getMore its own operation span, sibling to the cursor-creating operation's span. Driver-internal iteration adds no operation spans, no span is scoped to a cursor's lifetime, and a change stream resume ends the failed span while giving killCursors none. Drivers now MUST set db.mongodb.cursor_id on operation spans that create a cursor or operate on a single existing cursor. It is never a literal 0 , and for a getMore it holds the id the driver sent rather than the 0 the reply may return. Add spec tests from https://github.com/mongodb/specifications/commit/d1ac31b730d87c6cc18d126149da30008ef12561 and implement prose tests 3 and 4. Commits for syncing spec/prose tests https://github.com/mongodb/specifications/commit/d1ac31b730d87c6cc18d126149da30008ef12561 adds the two get_more fixtures, valid-pass/operator-gte as the reference test for the new operator, and prose tests 3 and 4. https://github.com/mongodb/mongo-python-driver/pull/2994 is the Python driver implementation. Context for other referenced/linked tickets DRIVERS-3627 tracks optional span links between the sibling getMore and cursor-creating operation spans. DRIVERS-3626 fixed MongoDB 4.2 server orchestration. Earlier patch runs for this ticket show two unrelated failures.
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This ticket was split from DRIVERS-3598, please see that ticket for a detailed description.

            Assignee:
            Unassigned
            Reporter:
            TPM Jira Automations Bot
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: