hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12197) Do the HDFS dist stitching in hadoop-hdfs-project
Date Mon, 31 Jul 2017 19:37:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-12197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107840#comment-16107840

Elek, Marton commented on HDFS-12197:

It's not just about running the pseudo distributed cluster from dev tree. It's also impossible
to run Namenode from IDE while the scope is provided for the selected dependencies. Would
be great to fix this as well.

> 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
> 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:
> 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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message