-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: manual
-
Labels:None
This is in relation to issues SERVER-6471.
The old behavior was that aggregation with the $min operator would consider a) values set to null and b) undefined values. Case a) would return the null value as the minimum. Case b) would prefer the "undefined" value as the minimum and thus undefine the value in the end result.
The new behavior is to skip both undefined and null values when comparing and therefore not considering them as being smaller than any of the "real" values.
The documentation on the aggregation $min operator is very short and doesn't mention any behavior in regard to null or undefined values. It needs to be updated and fleshed out for 2.4.
- is related to
-
SERVER-6471 aggregation $min uses Value ordering to compare null and undefined values, does not exclude null and undefined values from consideration
- Closed