-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Ensure the set of remote clusters is consistent over the life of ES|QL query #126000
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
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. Thanks Stas!
/** | ||
* Returns a set of currently configured remote clusters. | ||
*/ | ||
default Set<String> getConfiguredClusters() { |
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.
Can we avoid the default implementation here?
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.
We could but it would make some tests a lot more verbose.
💔 Backport failed
You can use sqren/backport to manually backport by running |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
…L query (elastic#126000) * Ensure the set of remote clusters is consistent over the life of ES|QL query (cherry picked from commit d84b65d) # Conflicts: # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/session/EsqlSession.java
…L query (elastic#126000) * Ensure the set of remote clusters is consistent over the life of ES|QL query
Even if the configuration changes in the middle of the query, we should use the same set of clusters throughout. This avoids various race conditions and eliminates the need for repeated resolution.