hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mingliang Liu (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-14498) HADOOP_OPTIONAL_TOOLS not parsed correctly
Date Tue, 06 Jun 2017 20:30:18 GMT
Mingliang Liu created HADOOP-14498:

             Summary: HADOOP_OPTIONAL_TOOLS not parsed correctly
                 Key: HADOOP-14498
                 URL: https://issues.apache.org/jira/browse/HADOOP-14498
             Project: Hadoop Common
          Issue Type: Bug
          Components: build
    Affects Versions: 3.0.0-alpha1
            Reporter: Mingliang Liu

# This will make hadoop-azure not show up in the hadoop classpath, though both hadoop-aws
and hadoop-azure-datalake are in the classpath.{code:title=hadoop-env.sh}
export HADOOP_OPTIONAL_TOOLS="hadoop-azure,hadoop-aws,hadoop-azure-datalake"
# And if we put only hadoop-azure and hadoop-aws, both of them are shown in the classpath.
export HADOOP_OPTIONAL_TOOLS="hadoop-azure,hadoop-aws"

This makes me guess that, while parsing the {{HADOOP_OPTIONAL_TOOLS}}, we make some assumptions
that hadoop tool modules have a single "-" in names, and the _hadoop-azure-datalake_ overrides
the _hadoop-azure_. Or any other assumptions about the {{${project.artifactId\}}}?

Ping [~aw].

This message was sent by Atlassian JIRA

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

View raw message