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

Changed behavior in SBE when filter is {"":null}

    XMLWordPrintable

Details

    • Fully Compatible
    • v5.0
    • Query Execution 2021-07-26, QE 2021-08-09, QE 2021-08-23, QE 2021-09-06, QE 2021-09-20

    Description

      On the legacy query engine (4.4, 5.0 with internalQueryForceClassicEngine), passing on a filter object with the form

      {"": null}

      evaluates as true and returns all docs.
      However on the new query engine it evaluates as false.

      This was observed by a test case with the Go Driver passing bson.D{{}} as the filter.
      Changing to bson.D{} (which translates to filter: {}) works around the issue.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-59757 Evaluate supporting queries with match expressions on empty field names in SBE

          • Major - P3 - Major loss of function.
          • Backlog
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-64123 $elemMatch value predicate causes queries to accidentally fall back to the classic engine

          • Major - P3 - Major loss of function.
          • Backlog

          Task - A task that needs to be done. SERVER-57758 Turn SBE off by default and invert the sense of the internalQueryForceClassicEngine flag

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              andrii.dobroshynski@mongodb.com Andrii Dobroshynski
              tomer.yakir@mongodb.com Tomer Yakir
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: