-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Aggregation Framework
-
None
-
ALL
We need to decide how we are going to handle cases where aggregation expressions do not have an obviously correct return type. For example, if the user applies $mod with a string or double as an argument, or if the user applies $add with a string and a date.
- duplicates
-
SERVER-6203 Aggregation operators should have well defined implicit type coercion behavior.
-
- Backlog
-
- is duplicated by
-
SERVER-11157 Type casting operator for aggregation (and query)
-
- Closed
-
- related to
-
SERVER-6165 use of an integer valued double with a $mod expression can produce an incorrect result
-
- Closed
-
-
SERVER-6125 aggregation $sort cannot process heterogenous data types (asserts)
-
- Closed
-
-
SERVER-6142 ExpressionCompare::evaluate does not use Value::compare, does not handle heterogenous types (including numeric types) and some other comparison cases
-
- Closed
-
-
SERVER-6184 mixing nested and dotted $project ExpressionObjects produces inconsistent results and assertions in some cases
-
- Closed
-
-
SERVER-6196 'can't add two dates together' assertion during constant folding
-
- Closed
-