[SERVER-31775] NaN comparison not aligned between query and pipeline Created: 31/Oct/17 Updated: 24/Jul/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | 3.4.10 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Simon | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | mql-semantics | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Participants: |
| Description |
|
The query comparison operators have a handled case for NaN This behavior is not aligned with the Comparison Aggregation Operators and provides different result when used i.e. in $match pipeline stage or in a $project stage. Query : src/mongo/db/matcher/expression_leaf.cpp
Pipeline: src/mongo/db/pipeline/value.cpp
|
| Comments |
| Comment by Simon [ 31/Oct/17 ] | ||||||||||
|
Test case:
| ||||||||||
| Comment by Mark Agarunov [ 31/Oct/17 ] | ||||||||||
|
Hello Uyttendaele, Thank you for the detailed example. I've set the fixVersion to "Needs Triage" for this new feature to be scheduled against our currently planned work. Updates will be posted on this ticket as they happen. Thanks, | ||||||||||
| Comment by Simon [ 31/Oct/17 ] | ||||||||||
|
Relates somehow to # |