Fix for {$size: 1} queries on non-existent fields #711
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #710 and looks related to the fixes in #697.
Currently, if a missing field is queried with
{field: {"$size": 1}}
, all documents without that field will match, asbool(NOTHING)
evaluates toTrue
.This PR checks explicitly whether the missing field
$size
isNOTHING
(indicating that the field value could not be parsed as an array, see #697).The first commit in this PR adds a test for the current bug (so the CI should fail), and the second provides the fix.