[
https://issues.apache.org/jira/browse/YARN-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359169#comment-14359169
]
Hadoop QA commented on YARN-1942:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704209/YARN-1942.1.patch
against trunk revision 06ce1d9.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6943//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6943//console
This message is automatically generated.
> Many of ConverterUtils methods need to have public interfaces
> -------------------------------------------------------------
>
> Key: YARN-1942
> URL: https://issues.apache.org/jira/browse/YARN-1942
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api
> Affects Versions: 2.4.0
> Reporter: Thomas Graves
> Assignee: Wangda Tan
> Priority: Critical
> Attachments: YARN-1942.1.patch
>
>
> ConverterUtils has a bunch of functions that are useful to application
> masters. It should either be made public or we make some of the utilities
> in it public or we provide other external apis for application masters to
> use. Note that distributedshell and MR are both using these interfaces.
> For instance the main use case I see right now is for getting the application
> attempt id within the appmaster:
> String containerIdStr =
> System.getenv(Environment.CONTAINER_ID.name());
> ConverterUtils.toContainerId
> ContainerId containerId = ConverterUtils.toContainerId(containerIdStr);
> ApplicationAttemptId applicationAttemptId =
> containerId.getApplicationAttemptId();
> I don't see any other way for the application master to get this information.
> If there is please let me know.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
