[
https://issues.apache.org/jira/browse/YARN-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390579#comment-15390579
]
Sunil G commented on YARN-5203:
-------------------------------
Thanks [~subru] for the details.
I rechecked this scenario. Majorly we use {{ResourceInfo}} in this patch, so
*capability* will have {{vCores}} instead earlier {{virtualCores}}. For
{{priority}}, we can consider this a bug fix as few clients may unmarshal as
jaxb object instead of strings. If so, could we mark a flag saying its a bug
fix and may have incompatible changes. So we can track if in case any issues.
Thoughts [~subru]/[~vvasudev] and [~ellenfkh].
> 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,
> YARN-5203.v2.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
