You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2018/10/01 12:31:00 UTC

[jira] [Commented] (HADOOP-15803) Make hadoop-aws an optional tool

    [ https://issues.apache.org/jira/browse/HADOOP-15803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633932#comment-16633932 ] 

Steve Loughran commented on HADOOP-15803:
-----------------------------------------

well, it's at least consistent, even though it's an odd level of compatibility.

it'll need documentation 

> Make hadoop-aws an optional tool
> --------------------------------
>
>                 Key: HADOOP-15803
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15803
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3
>            Reporter: Sean Mackrory
>            Priority: Major
>
> See HADOOP-15797 for some background. hadoop-aws is marked as both an optional and builtin module. It's only builtin so the 'hadoop s3guard' CLI can work. But I think if you're going to use 'hadoop s3guard' CLI you should just enable hadoop-aws in HADOOP_OPTIONAL_TOOLS. Let's just make sure it fails with a nice error message if you attempt anything otherwise.
> I suppose this may have some compatibility implications now that I think about it, but if we can avoid s3a being loaded every time, that would be a pretty big deal.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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