[
https://issues.apache.org/jira/browse/TEZ-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975886#comment-15975886
]
Junping Du commented on TEZ-3690:
---------------------------------
Hi [~sseth], that's a fair point. However, I found in HDFS-6200 description, it
indeed mentioned: "As discussed in the hdfs-dev mailing list
(http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-dev/201404.mbox/browser),
downstream projects are forced to bring in additional dependency in order to
access hdfs." So I think it could be HDFS community decision for this. CC
[~wheat9] and [~liuml07].
Just upload a quick fix for Tez in case needed.
> Tez on hadoop 3 build failed due to hdfs client/server jar separation
> ---------------------------------------------------------------------
>
> Key: TEZ-3690
> URL: https://issues.apache.org/jira/browse/TEZ-3690
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Junping Du
> Assignee: Junping Du
> Priority: Blocker
> Fix For: 0.9.0
>
> Attachments: TEZ-3690.patch
>
>
> Build TEZ master branch against hadoop 3 alpha 3 (trunk branch), and found
> issues:
> {noformat}
> ...
> api/src/test/java/org/apache/tez/common/TestTezCommonUtils.java:[62,42]
> cannot access org.apache.hadoop.hdfs.DistributedFileSystem
> {noformat}
> This is due to HDFS-6200 that we are separating client and server jars. We
> should fix downstream projects for this change.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
