-
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
Refactor ESQL CcsUtils #116121
Refactor ESQL CcsUtils #116121
Conversation
Pinging @elastic/es-analytical-engine (Team:Analytics) |
for (FieldCapabilitiesFailure failure : failures) { | ||
if (ExceptionsHelper.isRemoteUnavailableException(failure.getException())) { | ||
for (String indexExpression : failure.getIndices()) { | ||
if (indexExpression.indexOf(RemoteClusterAware.REMOTE_CLUSTER_INDEX_SEPARATOR) > 0) { |
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.
Are index expressions already parsed here? E.g. remote/index wildcards, etc.?
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.
Yes. It is called in IndexResolver after calling field-caps. It sifts through the FieldCapsResponse failure list.
This is not new code. I just moved this method out of IndexResolver into the utils method, as Costin had requested in my earlier PR.
💚 Backport successful
|
Pure refactoring PR
Pure refactoring PR
Pure refactoring PR
Finalized refactorings from closed PR https://github.com/elastic/elas…ticsearch/pull/115976
This is a pure refactoring PR. No new code has been added other than two new tests in
EsqlSessionCCSUtilsTests.java
.