[ 
https://issues.apache.org/jira/browse/YARN-9401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806863#comment-16806863
 ] 

Weiwei Yang commented on YARN-9401:
-----------------------------------

The output looks good. But I think [~yufeigu] raise a good point, it seems 
{{VersionInfo}} was used in both HDFS/MR/YARN, they return same Hadoop version. 
It will make it inconsistent if this change is only made to YARN. I don't think 
we should change this, before we cleanly separate these projects. It's a bit 
overlap, but rightnow {{YarnVersionInfo}} was only used in web-app.

> Fix `yarn version` print the version info is the same as `hadoop version`
> -------------------------------------------------------------------------
>
>                 Key: YARN-9401
>                 URL: https://issues.apache.org/jira/browse/YARN-9401
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>            Reporter: Wanqiang Ji
>            Assignee: Wanqiang Ji
>            Priority: Minor
>         Attachments: YARN-9401.001.patch, YARN-9401.002.patch
>
>
> It's caused by in `yarn` shell used `org.apache.hadoop.util.VersionInfo` 
> instead of `org.apache.hadoop.yarn.util.YarnVersionInfo` as the 
> `HADOOP_CLASSNAME` by mistake.
> {panel:title=Before}
> Hadoop 3.3.0-SNAPSHOT
> Source code repository [https://github.com/apache/hadoop.git] -r 
> 53a86e2b8ecb83b666d4ed223fc270e1a46642c1
> Compiled by jiwq on 2019-04-01T04:55Z
> Compiled with protoc 2.5.0
> From source with checksum 829bd6e22c17c6da74f5c1a61647922
> {panel}
> {panel:title=After}
> YARN 3.3.0-SNAPSHOT
> Subversion [https://github.com/apache/hadoop.git] -r 
> 53a86e2b8ecb83b666d4ed223fc270e1a46642c1
> Compiled by jiwq on 2019-04-01T05:06Z
> From source with checksum e10a192bd933ffdafe435d7fe99d24d
> {panel}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to