[
https://issues.apache.org/jira/browse/YARN-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385099#comment-15385099
]
Subru Krishnan commented on YARN-5203:
--------------------------------------
[~sunilg], thanks for taking a look and bringing up the important point on
compatibility.
IIUC unfortunately we cannot continue to have the raw RRs as JAXB will not be
able to unmarshal directly to {{AppInfo}} object. Today it works because
existing clients like UI deserialize directly to _String_ which should continue
to work even if we use JAXB object for RRs.
[~ellenfkh], can you kindly do a quick validation as you have a setup where you
already have been testing extensively. Thanks!
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
