YARN-11893. Extend REST API error messages with exception classes #8066
+59 −58
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.
Change-Id: I7c08bd438fe17dfed8641f6883d8dbc9566fc771
Description of PR
In GenericExceptionHandler's toResponse method we put only the exception message into the RemoteExceptionData object.
It would be a bit more informative if we would use throwable.toString() instead of throwable.getMessage() as the former extends the error message with the exception class as well, similarly to previous versions.
How was this patch tested?
Tested on a Hadoop cluster
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?