hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Mackrory (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-15797) optional / builtin modules confused for cloud storage
Date Thu, 27 Sep 2018 18:35:00 GMT
Sean Mackrory created HADOOP-15797:

             Summary: optional / builtin modules confused for cloud storage
                 Key: HADOOP-15797
                 URL: https://issues.apache.org/jira/browse/HADOOP-15797
             Project: Hadoop Common
          Issue Type: Bug
          Components: fs/adl, fs/azure, fs/s3
            Reporter: Sean Mackrory

Throwing this in your .hadooprc results in hadoop-aws being in the classpath but not hadoop-azure*:

hadoop_add_to_classpath_tools hadoop-aws
hadoop_add_to_classpath_tools hadoop-azure
hadoop_add_to_classpath_tools hadoop-azure-datalake

It would seem that the core issue is that that requires the module to have listed it's dependencies
in MODULE_NAME.tools-builtin.txt, whereas the Azure connectors only have them listed in MODULE_NAME.tools-optional.txt.
S3 does both, and there's a comment in it's POM about how it needs to do this because of the
"hadoop s3guard" CLI.

Maybe there's some history that I'm missing here, but I think what's wrong here is that hadoop_add_to_classpath
should get what it needs from optional modules. builtin modules shouldn't even need hadoop_add_to_classpath
to be added anyway.

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