-
Notifications
You must be signed in to change notification settings - Fork 25.6k
ESQL: Fix lookup test result ordering #120622
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESQL: Fix lookup test result ordering #120622
Conversation
Also, re-order the test cases to remain consistent: put all the multi-match tests next to the multi-value and null match tests.
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
| ; | ||
|
|
||
| repeatedIndexOnFrom | ||
| required_capability: join_lookup_v11 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just moved out of the multi-match tests.
| ; | ||
|
|
||
| ########################################################################### | ||
| # null and multi-value behavior with languages_lookup_non_unique_key index |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Entire section moved up to be next to the multi-match tests.
| nonUniqueRightKeyOnTheCoordinatorCorrectOrdering | ||
| // Same as above, but don't ignore the order completely. At least the emp_no col must remain correctly ordered. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one is new, because above we have to ignore the ordering and thus don't test that the left key ordering remains stable. This test does.
|
|
||
| mvJoinKeyOnFrom | ||
| required_capability: join_lookup_v11 | ||
| required_capability: join_lookup_skip_mv |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ivancea , I thought I'll fix this one while I'm at it.
💔 Backport failed
You can use sqren/backport to manually backport by running |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
Fix elastic#120600 Fix elastic#120601 Fix elastic#120602 Fix elastic#120603 Fix elastic#120658 Fix elastic#120659 While I was at it, I moved the LOOKUP JOINs test cases with multiple right keys next to the test cases with multivalues and nulls in keys to be consistent and make stuff more easy to find. (cherry picked from commit b985b3e) # Conflicts: # muted-tests.yml
Fix #120600 Fix #120601 Fix #120602 Fix #120603 Fix #120658 Fix #120659 While I was at it, I moved the LOOKUP JOINs test cases with multiple right keys next to the test cases with multivalues and nulls in keys to be consistent and make stuff more easy to find. (cherry picked from commit b985b3e) # Conflicts: # muted-tests.yml
Fix #120600
Fix #120601
Fix #120602
Fix #120603
Fix #120658
Fix #120659
While I was at it, I moved the LOOKUP JOINs test cases with multiple right keys next to the test cases with multivalues and nulls in keys to be consistent and make stuff more easy to find.