[SERVER-6571] Replace use of Undefined as missing with EOO in aggregation Created: 24/Jul/12 Updated: 11/Jul/16 Resolved: 11/Dec/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 2.3.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
Undefined is a valid data type and shouldn't be used for missing values. I know it is used as such in ExpressionFieldPath and ExpressionObject. @Matt: could you search for any other uses of Undefined BSONType and see how feasible this is? |
| Comments |
| Comment by Mathias Stearn [ 11/Dec/12 ] |
|
Undefined is now considered a proper user-defined value to be preserved, different from missing Values. |
| Comment by auto [ 11/Dec/12 ] |
|
Author: {u'date': u'2012-12-05T23:55:25Z', u'email': u'mathias@10gen.com', u'name': u'Mathias Stearn'}Message: Normalize handling of Undefined vs EOO/missing in agg Related tickets: |
| Comment by Mathias Stearn [ 31/Jul/12 ] |
|
Bumping to 2.3 since I don't think this is the best solution, but something similar is needed. |