Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-5617

Fix Failing Explain Tests

XMLWordPrintableJSON

    • Type: Icon: Build Failure Build Failure
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.9.1, 6.2.0
    • Affects Version/s: 6.0.0, 5.8.1, 4.17.1
    • Component/s: None
    • 2
    • Not Needed
    • Hide

      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.

      Show
      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      The latest server version, 7.1.0-alpha0-269-g2deea5b, started returning back explain version 2 documents in some of our tests on sharded clusters, which causes them to fail as we are asserting that a top level field (queryPlanner) exists that is no longer present there.

      Build failure: https://spruce.mongodb.com/task/mongo_node_driver_next_rhel80_large_Node20_test_latest_load_balanced_patch_177a4fc0226dc9ea15de8d37cc0cb7d6a423f838_64f9faf83627e0b0a9d321b7_23_09_07_16_31_54/logs?execution=0&sortBy=STATUS&sortDir=ASC

      This will continue to change in the future, see PM-2517 so we should change the assertions in our tests to not depend on specific fields.

      AC:

      • Change the aggregation explain tests in test/integration/crud/explain.test.ts tests to check for "queryPlanner" presence regardless of exact location
      • Change the aggregation cursor explain tests in test/integration/crud/aggregation.test.ts to check for "executionStats.allPlansExecution" presence regardless of exact location

        There are no Sub-Tasks for this issue.

            Assignee:
            durran.jordan@mongodb.com Durran Jordan
            Reporter:
            durran.jordan@mongodb.com Durran Jordan
            Bailey Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: