[
https://issues.apache.org/jira/browse/YARN-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388622#comment-15388622
]
Subru Krishnan commented on YARN-5203:
--------------------------------------
[~sunilg], I think present clients are all unmarshalling as Strings as
otherwise they would hit this issue (like we did). For those clients, there is
a potential problem if they do manually parsing of the internal
_resourceRequests_ [string
contents|https://issues.apache.org/jira/browse/YARN-5203?focusedCommentId=15370535].
I (obviously) feel that this is esoteric and moreover block any clients (like
Federation Router) clients that want to use JAXB and expect proper objects
back. So I feel we should be OK to ignore this scenario. Do this make sense?
> Return ResourceRequest JAXB object in ResourceManager Cluster Applications
> REST API
> -----------------------------------------------------------------------------------
>
> Key: YARN-5203
> URL: https://issues.apache.org/jira/browse/YARN-5203
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Subru Krishnan
> Assignee: Ellen Hui
> Attachments: YARN-5203.v0.patch, YARN-5203.v1.patch
>
>
> The ResourceManager Cluster Applications REST API returns {{ResourceRequest}}
> as String rather than a JAXB object. This prevents downstream tools like
> Federation Router (YARN-3659) that depend on the REST API to unmarshall the
> {{AppInfo}}. This JIRA proposes updating {{AppInfo}} to return a JAXB version
> of the {{ResourceRequest}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
