Skip to content

Conversation

smalyshev
Copy link
Contributor

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.

@smalyshev smalyshev added :Analytics/ES|QL AKA ESQL v8.19.0 auto-backport Automatically create backport pull requests when merged >refactoring labels Apr 1, 2025
@smalyshev smalyshev marked this pull request as ready for review April 1, 2025 00:48
@smalyshev smalyshev requested review from dnhatn and quux00 April 1, 2025 00:48
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-analytical-engine (Team:Analytics)

@elasticsearchmachine elasticsearchmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Apr 1, 2025
Copy link
Member

@dnhatn dnhatn left a 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() {
Copy link
Member

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?

Copy link
Contributor Author

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.

@smalyshev smalyshev merged commit d84b65d into elastic:main Apr 2, 2025
17 checks passed
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.x Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 126000

@smalyshev
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
8.x

Questions ?

Please refer to the Backport tool documentation

smalyshev added a commit to smalyshev/elasticsearch that referenced this pull request Apr 2, 2025
…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
elasticsearchmachine pushed a commit that referenced this pull request Apr 2, 2025
…L query (#126000) (#126161)

* 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
andreidan pushed a commit to andreidan/elasticsearch that referenced this pull request Apr 9, 2025
…L query (elastic#126000)

* Ensure the set of remote clusters is consistent over the life of ES|QL query
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Analytics/ES|QL AKA ESQL auto-backport Automatically create backport pull requests when merged >refactoring Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v8.19.0 v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants