Zhijie Shen commented on YARN-3721:

+1 for the approach.

BTW, there always exists a risk: HBase is the downstream of Hadoop, and compile 
against certain version of Hadoop. Say we use HBase X.X.X, and it depends on 
Hadoop Y.Y.Y. However, on trunk/branch-2, if we have made some incompatible 
change  to mini dfs cluster for a later release Y.Y.Z, our test cases are very 
likely to be broken, because HBase test utils compiled against Y.Y.Y is not 
longer compatible with Y.Y.Z runtime libs.

> build is broken on YARN-2928 branch due to possible dependency cycle
> --------------------------------------------------------------------
>                 Key: YARN-3721
>                 URL: https://issues.apache.org/jira/browse/YARN-3721
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Sangjin Lee
>            Assignee: Li Lu
>            Priority: Blocker
>         Attachments: YARN-3721-YARN-2928.001.patch, 
> YARN-3721-YARN-2928.002.patch, YARN-3721-YARN-2928.002.patch
> The build is broken on the YARN-2928 branch at the 
> hadoop-yarn-server-timelineservice module. It's been broken for a while, but 
> we didn't notice it because the build happens to work despite this if the 
> maven local cache is not cleared.
> To reproduce, remove all hadoop (3.0.0-SNAPSHOT) artifacts from your maven 
> local cache and build it.
> Almost certainly it was introduced by YARN-3529.

This message was sent by Atlassian JIRA

Reply via email to