[
https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wangda Tan updated YARN-5270:
-----------------------------
Attachment: YARN-5270-branch-2.001.patch
Thanks [~kasha],
[~sseth] offline mentioned that YARN-4844 breaks binary compatibility as well,
according to Java compatibility doc, change parameter types in signature causes
method cannot find issue. That means if we run a YARN application compiled
against Hadoop 2.7 in a Hadoop 2.8 deployment, it fails.
What I have done in this patch:
- Added {{long getMemorySize}} and kept {{int getMemory}}
- Removed {{long getVirtualCoresSize}} and kept {{int setVirtualCores}}
- Other changes like wrong type converting issues in Resources class.
> Solve miscellaneous issues caused by YARN-4844
> ----------------------------------------------
>
> Key: YARN-5270
> URL: https://issues.apache.org/jira/browse/YARN-5270
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Priority: Blocker
> Attachments: YARN-5270-branch-2.001.patch
>
>
> Such as javac warnings reported by YARN-5077 and type converting issues in
> Resources class.
--
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
