-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Refactor remote cluster handling in Analyzer #126426
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
Conversation
- Initialize clusters earlier - Simplify cluster set calculation - No need to keep separate skipped list for enrich resolution
7a350a8
to
23bd44c
Compare
23bd44c
to
89c781c
Compare
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
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
💔 Backport failed
You can use sqren/backport to manually backport by running |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
* Refactor remote cluster handling in Analyzer - Initialize clusters earlier - Simplify cluster set calculation - No need to keep separate skipped list for enrich resolution (cherry picked from commit b21e325) # Conflicts: # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/session/EsqlSession.java
* Refactor remote cluster handling in Analyzer - Initialize clusters earlier - Simplify cluster set calculation - No need to keep separate skipped list for enrich resolution (cherry picked from commit b21e325) # Conflicts: # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/session/EsqlSession.java
This reverts commit b21e325.
This helps clean up the code in preparation for enabling remote lookup indices (needed for LOOKUP JOIN).