Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
Query 2018-10-08, Query 2018-10-22
Description
Query planner unit tests will currently pass when the test provides bounds that are a subset of the actual bounds used by the planner. For instance, when performing the query {x: {$in: [1,2]}} you can provide the bounds {'x': [[1,1,true,true]]} and a test will pass where the bounds generated are really {'x': [[1,1,true,true], [2,2,true,true]]}.
While for a small number of our tests (mainly geo) it is useful to be able to provide a subset of bounds and confirm that they match, most would benefit from strict checks. We should make the default strict and allow those tests that require it to specify that only those provided are to be confirmed.