[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:
Related
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:
SERVER-6571 replace use of Undefined as missing with EOO
SERVER-6471 ignore nullish values in $min and $max accumulators
SERVER-6144 divide by zero makes field disappear (this solution isn't final)
Branch: master
https://github.com/mongodb/mongo/commit/459467c7cf47b57d8990eeb41c65b4e203e15b65

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.

Generated at Thu Feb 08 03:12:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.