-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Fix listener usage in remote clusters #122629
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) |
| return ActionListener.runAfter(delegate.delegateResponse((inner, e) -> { | ||
| taskManager.cancelTaskAndDescendants(groupTask, reason, true, ActionListener.running(() -> { | ||
| EsqlCCSUtils.skipUnavailableListener(delegate, executionInfo, clusterAlias, EsqlExecutionInfo.Cluster.Status.PARTIAL) | ||
| EsqlCCSUtils.skipUnavailableListener(inner, executionInfo, clusterAlias, EsqlExecutionInfo.Cluster.Status.PARTIAL) |
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.
Looking at the code, it seems like inner and delegate in this case are the same thing, am I wrong?
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 should, but it's more idiomatic to use the inner listener.
|
@idegtiarenko @smalyshev Thanks for reviews. |
We should notify the listener provided in delegateResponse/delegateFailure, not the original listener.
💚 Backport successful
|
We should notify the listener provided in delegateResponse/delegateFailure, not the original listener.