[DOCS-974] Document new aggregation $min behavior in 2.4 of skipping null and undefined values Created: 11/Jan/13 Updated: 16/Mar/13 Due: 19/Mar/13 Resolved: 16/Mar/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | mongodb-2.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Thomas Rueckstiess | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 10 years, 48 weeks, 4 days ago | ||||||||
| Description |
|
This is in relation to issues 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. |
| Comments |
| Comment by auto [ 16/Mar/13 ] |
|
Author: {u'date': u'2013-03-16T14:33:04Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: merge: |
| Comment by auto [ 16/Mar/13 ] |
|
Author: {u'date': u'2013-03-16T00:49:44Z', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |