[SERVER-81048] Possible Date Precision Bug in 6.0.10 Created: 13/Sep/23 Updated: 27/Oct/23 Resolved: 28/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Query Execution |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Patrick Meredith | Assignee: | Projjal Chanda |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | QE 2023-10-02 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
This error came up in our normal BI Connector tdvt waterfall tests. If this is an intentional change, we can fix the tests on our end, but there has been a change in date math between 6.0.9 and 6.0.10. This is only occurring on 6.0.10, however, while working fine in 6.2 (we are not yet running this test on 7.0). I've reduced the test case down here to a fairly minimal query. The sort is just to make the results easier to compare. The dataset itself is encoded in the test. $num4 is is a double that is conditionally $floored or $ceil'd and subtracted from the $date0 field, which is a date. I can confirm all the $floor and $ceil calculations are the same between versions, so it's coming down to date $subtract. The outputs are differing by .001 second for two of the five documents in the result
The results for 6.0.9 are:
While the results for 6.0.10 are:
|
| Comments |
| Comment by Patrick Meredith [ 02/Oct/23 ] |
|
projjal.chanda@mongodb.com thank you, I thought this may be "works as designed". We'll update the test so this isn't flagged in the future. |
| Comment by Projjal Chanda [ 28/Sep/23 ] |
|
Hi patrick.meredith@mongodb.com. This is due to an expected behavior change from |
| Comment by Amr Elhelw [ 19/Sep/23 ] |
|
Seems related to |