-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Populate cross cluster info after index resolution #137317
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
Draft
idegtiarenko
wants to merge
4
commits into
elastic:main
Choose a base branch
from
idegtiarenko:init_esql_execution_info
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -544,19 +544,10 @@ private void resolveIndicesAndAnalyze( | |
| PreAnalysisResult result, | ||
| ActionListener<Versioned<LogicalPlan>> logicalPlanListener | ||
| ) { | ||
| EsqlCCSUtils.initCrossClusterState( | ||
| indicesExpressionGrouper, | ||
| verifier.licenseState(), | ||
| preAnalysis.indexes().keySet(), | ||
| executionInfo | ||
| ); | ||
|
|
||
| SubscribableListener.<PreAnalysisResult>newForked( | ||
| // The main index pattern dictates on which nodes the query can be executed, so we use the minimum transport version from this | ||
| // field | ||
| // caps request. | ||
| l -> preAnalyzeMainIndices(preAnalysis.indexes().entrySet().iterator(), preAnalysis, executionInfo, result, requestFilter, l) | ||
| ).andThenApply(r -> { | ||
| EsqlCCSUtils.checkLicense(executionInfo, verifier.licenseState()); | ||
| if (r.indexResolution.isEmpty() == false // Rule out ROW case with no FROM clauses | ||
| && executionInfo.isCrossClusterSearch() | ||
| && executionInfo.getRunningClusterAliases().findAny().isEmpty()) { | ||
|
|
@@ -844,38 +835,36 @@ private void preAnalyzeMainIndices( | |
| ThreadPool.Names.SEARCH_COORDINATION, | ||
| ThreadPool.Names.SYSTEM_READ | ||
| ); | ||
| // TODO: This is not yet index specific, but that will not matter as soon as #136804 is dealt with | ||
| if (executionInfo.clusterAliases().isEmpty()) { | ||
| // return empty resolution if the expression is pure CCS and resolved no remote clusters (like no-such-cluster*:index) | ||
| listener.onResponse( | ||
| result.withIndices(indexPattern, IndexResolution.valid(new EsIndex(indexPattern.indexPattern(), Map.of(), Map.of()))) | ||
| ); | ||
| } else { | ||
| indexResolver.resolveAsMergedMappingAndRetrieveMinimumVersion( | ||
| indexPattern.indexPattern(), | ||
| result.fieldNames, | ||
| // Maybe if no indices are returned, retry without index mode and provide a clearer error message. | ||
| switch (indexMode) { | ||
| case IndexMode.TIME_SERIES -> { | ||
| var indexModeFilter = new TermQueryBuilder(IndexModeFieldMapper.NAME, IndexMode.TIME_SERIES.getName()); | ||
| yield requestFilter != null | ||
| ? new BoolQueryBuilder().filter(requestFilter).filter(indexModeFilter) | ||
| : indexModeFilter; | ||
| } | ||
| default -> requestFilter; | ||
| }, | ||
| indexMode == IndexMode.TIME_SERIES, | ||
| preAnalysis.useAggregateMetricDoubleWhenNotSupported(), | ||
| preAnalysis.useDenseVectorWhenNotSupported(), | ||
| listener.delegateFailureAndWrap((l, indexResolution) -> { | ||
| EsqlCCSUtils.updateExecutionInfoWithUnavailableClusters(executionInfo, indexResolution.inner().failures()); | ||
| l.onResponse( | ||
| result.withIndices(indexPattern, indexResolution.inner()) | ||
| .withMinimumTransportVersion(indexResolution.minimumVersion()) | ||
| ); | ||
| }) | ||
| ); | ||
| } | ||
| indexResolver.resolve( | ||
| indexPattern.indexPattern(), | ||
| result.fieldNames, | ||
| // Maybe if no indices are returned, retry without index mode and provide a clearer error message. | ||
| switch (indexMode) { | ||
| case IndexMode.TIME_SERIES -> { | ||
| var indexModeFilter = new TermQueryBuilder(IndexModeFieldMapper.NAME, IndexMode.TIME_SERIES.getName()); | ||
| yield requestFilter != null ? new BoolQueryBuilder().filter(requestFilter).filter(indexModeFilter) : indexModeFilter; | ||
| } | ||
| default -> requestFilter; | ||
| }, | ||
| indexMode == IndexMode.TIME_SERIES, | ||
| preAnalysis.useAggregateMetricDoubleWhenNotSupported(), | ||
| preAnalysis.useDenseVectorWhenNotSupported(), | ||
| listener.delegateFailureAndWrap((l, indexResolution) -> { | ||
| EsqlCCSUtils.initCrossClusterInfo(indicesExpressionGrouper, verifier.licenseState(), indexPattern, executionInfo); | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Here the state will be populated from field caps |
||
| EsqlCCSUtils.updateExecutionInfoWithUnavailableClusters(executionInfo, indexResolution.inner().failures()); | ||
|
|
||
| // today empty index resolution is not allowed unless it is caused by selecting from empty sets of remotes | ||
| if (executionInfo.clusterAliases().isEmpty() && indexResolution.inner().isValid() == false) { | ||
| indexResolution = new Versioned<>(IndexResolution.empty(indexPattern.indexPattern()), indexResolution.minimumVersion()); | ||
| } | ||
|
|
||
| // The main index pattern dictates on which nodes the query can be executed, | ||
| // so we use the minimum transport version from this field caps request. | ||
| l.onResponse( | ||
| result.withIndices(indexPattern, indexResolution.inner()).withMinimumTransportVersion(indexResolution.minimumVersion()) | ||
| ); | ||
| }) | ||
| ); | ||
| } | ||
|
|
||
| private void analyzeWithRetry( | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 not longer the case. We could have 2 distinct views targeting the same remote. In such case, their expressions are going to be concatenated.