Description:

Prior to this patch a query could be run with $min and $max values that were identical. As $min is inclusive and $max is exclusive, this would always result in an empty range. May be worth documenting that $max must always be greater than $min.

Scope of changes:

• meta/min
• meta/max
• cursor/min
• cursor max
• 4.0-compatibility

(for backports – just do pull request for releases not out yet)

Impact to other docs outside of this product:

none

MVP:

Resources:

Engineering Ticket Description:

As the max value is an exclusive bound, setting min and max to the same value will match nothing, even when an index exists that supports the key provided.