[
https://issues.apache.org/jira/browse/HDFS-12197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802479#comment-17802479
]
Shilun Fan commented on HDFS-12197:
-----------------------------------
Bulk update: moved all 3.4.0 non-blocker issues, please move back if it is a
blocker. Retarget 3.5.0.
> Do the HDFS dist stitching in hadoop-hdfs-project
> -------------------------------------------------
>
> Key: HDFS-12197
> URL: https://issues.apache.org/jira/browse/HDFS-12197
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.0.0-alpha4
> Reporter: Andrew Wang
> Priority: Major
>
> Problem reported by [~lars_francke] on HDFS-11596. We can no longer easily
> start a namenode and datanode from the source directory without doing a full
> build per the wiki instructions:
> https://wiki.apache.org/hadoop/HowToSetupYourDevelopmentEnvironment
> This is because we don't have a top-level dist for HDFS. $HADOOP_YARN_HOME
> for instance can be set to {{hadoop-yarn-project/target}}, but
> $HADOOP_HDFS_HOME goes into the submodule:
> {{hadoop-hdfs-project/hadoop-hdfs/target}}. This means it's missing the files
> from the sibling hadoop-hdfs-client module (which is required by the
> namenode), but also other siblings like nfs and httpfs.
> So, I think the right fix is doing the dist stitching at the
> {{hadoop-hdfs-project}} level where we can aggregate all the child modules,
> and pointing $HADOOP_HDFS_HOME at this directory.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
