-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[FEATURE] Fix up feature branch after merging master #40094
[FEATURE] Fix up feature branch after merging master #40094
Conversation
This is possible because there are no BWC concerns
Pinging @elastic/ml-core |
@@ -107,6 +104,8 @@ public void writeTo(StreamOutput out) throws IOException { | |||
if (parsingException != null) { // Do we have a parsing error? Throw it | |||
if (parsingException instanceof IOException) { | |||
throw (IOException) parsingException; | |||
} else if (parsingException instanceof RuntimeException) { | |||
throw (RuntimeException) parsingException; |
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.
I added this bit because almost all exceptions used in Elasticsearch are RuntimeException
s and the bit below that wraps in an ElasticsearchException
with no message is not great from the point of view of readability of error responses.
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.
LGTM
Jenkins run elasticsearch-ci/packaging-sample |
The failing packaging test is failing on master too at the moment. Since this PR is only merging to the feature branch I'll merge anyway. |
Feature branch PR
Incorporates feedback from #40060 (review)