-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Fix ActionListener.map exception handling #50886
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
Merged
henningandersen
merged 12 commits into
elastic:master
from
henningandersen:fix_map_exception_handling
Jan 29, 2020
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
09b5576
Fix ActionListener.map exception handling
henningandersen 3087981
Fix checkstyle
henningandersen 198651b
Add javadoc
henningandersen 62eaedc
Fix SearchTransportService DFS action
henningandersen 15e4199
Try assert
henningandersen 2b24d57
Adapt to asserting on failure.
henningandersen 0dae4f4
Remove test that cannot live with assertion error.
henningandersen b62a2b7
Merge remote-tracking branch 'origin/master' into fix_map_exception_h…
henningandersen 65ba493
Merge remote-tracking branch 'origin/master' into fix_map_exception_h…
henningandersen ca31964
Review comments
henningandersen 084790e
Merge remote-tracking branch 'origin/master' into fix_map_exception_h…
henningandersen 534c2bc
Armins improved javadoc
henningandersen 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
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.
ChannelActionListeneralso has this weird double-sending logic.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, but the code used to propagate the exception out. This seemed to be a left-over from when the
ChannelActionListenerwas introduced. The oldmapexception handling would ensureonFailurewere called on exception. This means this change is effectively a no-op now (with the caveat thatonFailurewill be called on exceptions like for all otherChannelActionListenerusages).We should notice that
DirectTransportChannelwill not bubble out exceptions from invoking theTransportResponseHandler. So it seems likely that the primary exceptions bubbled out are related to communicating the response over a wire, in which case invokingonFailuremight be desirable (for instance an NPE on serialization).So I would like to keep using
ChannelActionListenerhere and then deal withChannelActionListenerin a follow-up. WDYT?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.
++