[
https://issues.apache.org/jira/browse/YARN-11893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036223#comment-18036223
]
ASF GitHub Bot commented on YARN-11893:
---------------------------------------
p-szucs opened a new pull request, #8066:
URL: https://github.com/apache/hadoop/pull/8066
Change-Id: I7c08bd438fe17dfed8641f6883d8dbc9566fc771
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### 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:
- [x] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> Extend REST API error messages with exception classes
> -----------------------------------------------------
>
> Key: YARN-11893
> URL: https://issues.apache.org/jira/browse/YARN-11893
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: yarn, yarn-common
> Affects Versions: 3.5.0
> Reporter: Peter Szucs
> Assignee: Peter Szucs
> Priority: Minor
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]