[SERVER-83272] Fix discrepancy in sorting between classic and SBE Created: 15/Nov/23 Updated: 16/Nov/23 Resolved: 16/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Foteini Alvanaki | Assignee: | Foteini Alvanaki |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: | Create the following three collections
Run the following queries both in Classic and in SBE
Results in classic are always the same
Results in SBE for each query are t01
t02
t03
From my investigation this happens because in SBE when querying collections t01 and t03 we compare {
vs
but when we query t02 we compare
vs
The sort key in classic is in all relations
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Linked BF Score: | 5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
When we run a query in classic with a sort stage the order of the results does not depend in the order of the fields in the documents. When we run the same queries in SBE we see that the order of the results changes when the order of the fields in the documents changes. |
| Comments |
| Comment by Foteini Alvanaki [ 16/Nov/23 ] |
|
This discrepancy is considered acceptable. |
| Comment by Foteini Alvanaki [ 15/Nov/23 ] |
|
According to the test, it seems that this issue is acceptable since the fuzzer has a method ` |