[
https://issues.apache.org/jira/browse/HADOOP-15797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632749#comment-16632749
]
Sean Mackrory commented on HADOOP-15797:
----------------------------------------
Makes sense to me. I'll close this and file a separate one to see if there's a
good way to have the "hadoop s3guard" CLI command exist without hadoop-aws
being marked as a required module. If the command exists but fails with a nice
error message if someone tries to use it without adding hadoop-aws to
HADOOP_OPTIONAL_TOOLS, that would be good enough for me.
> 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
> Affects Versions: 3.2.0, 3.1.1
> Reporter: Sean Mackrory
> Priority: Major
>
> Throwing this in your .hadooprc results in hadoop-aws being in the classpath
> but not hadoop-azure*:
> {quote}
> hadoop_add_to_classpath_tools hadoop-aws
> hadoop_add_to_classpath_tools hadoop-azure
> hadoop_add_to_classpath_tools hadoop-azure-datalake
> {quote}
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
