Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-90195

Consider adding a fuzzer (or similar) to test the express path

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • Fully Compatible
    • QE 2024-07-08, QE 2024-07-22, QE 2024-08-05, QE 2024-08-19, QE 2024-09-02, QE 2024-09-16, QE 2024-09-30, QE 2024-10-14, QE 2024-10-28, QE 2024-11-11, QE 2024-11-25, QE 2024-12-09, QE 2024-12-23, QE 2025-01-06, QE 2025-01-20, QE 2025-02-03, QE 2025-02-17, QE 2025-03-03

      The set of operators eligible to use the express path is small. For this reason, we don't get a ton of passthrough coverage from existing jstests that are not specifically geared towards testing the express path.

      We should consider adding a fuzzer, or something else that's more aligned with PM-3714/WRITING-16826, to test the express path.

      Unclear if this should belong to QO or QE. Who will own the express path going forward?

            Assignee:
            colin.stolley@mongodb.com Colin Stolley
            Reporter:
            hana.pearlman@mongodb.com Hana Pearlman
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: