[SERVER-44717] MinKey > MaxKey in agg language Created: 18/Nov/19 Updated: 06/Dec/22 Resolved: 19/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Patrick Meredith | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | qopt-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Participants: | |||||||||
| Description |
|
I was checking the sanity of how we have been merging missing and null using {$lte: ['$foo', null]}. On the bright side, it works, on the down side it appears that minKey is > maxKey (and all other values).
It appears related to this: My assumption is that somewhere we are treating BSONType as unsigned, so that -1 becomes MAX_INT. |
| Comments |
| Comment by Patrick Meredith [ 19/Nov/19 ] | ||||||||||
|
kevin.pulocraig.homaYep, looks like this is it! Much better than having to track down where something would have been accidentally cast to unsigned. The new shell should presumably fix these issues once it's done. | ||||||||||
| Comment by Craig Homa [ 19/Nov/19 ] | ||||||||||
|
Hey patrick.meredith, looks like Kevin diagnosed the issue and provided the work-around. Please give that a try and let us know if you are still having an issue with it. | ||||||||||
| Comment by Kevin Pulo [ 18/Nov/19 ] | ||||||||||
|
This is
| ||||||||||
| Comment by Carl Champain (Inactive) [ 18/Nov/19 ] | ||||||||||
|
Passing this ticket along to the Query team. |