-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Add missing capability #120771
Add missing capability #120771
Conversation
@@ -31,7 +31,6 @@ setup: | |||
settings: | |||
index: | |||
mode: lookup | |||
number_of_shards: 1 |
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 is unrelated but should no longer be required, see #119059
Pinging @elastic/es-analytical-engine (Team:Analytics) |
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.
LGTM
I see other JOIN related capabilities check that JOIN_LOOKUP_V11 is enabled instead of checking on snapshot. An alternative could be LOOKUP_JOIN_TEXT(JOIN_LOOKUP_V11.isEnabled())
, but I think the two are equivalent at this stage
💚 Backport successful
|
191_lookup_join_text.yml
does not declarejoin_lookup_v11
.This causes
yamlRestCompatTest
test to fail for prs where a basic lookup join behavior is changed (for example in #120494) and above capability is incremented.