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

ASF GitHub Bot commented on HADOOP-19696:
-----------------------------------------

steveloughran opened a new pull request, #8094:
URL: https://github.com/apache/hadoop/pull/8094

   
   
   This moves all the cloud connector libraries to common/lib There are 
specific build options to control which libraries to include The hadoop-* JARs 
of the modules are includes, but dependencies are only included when the 
build-time options specify it.
   
     Available package profiles:
       hadoop-aliyun-package
       hadoop-aws-package
       hadoop-azure-datalake-package
       hadoop-cos-package
       hadoop-huaweicloud-package
   
   This means that by default AWS bundle.jar is no longer included in the 
distribution: to add it users must drop their chosen version of the SDK into 
share/hadoop/common/lib
   
   Anyone building their own release now has a choice of which connectors to 
bundle. The ASF ones will stay fairly lean to reduce the CVE attack surface as 
well as keep package size under control.
   
   This is the branch-3.4 variant which cuts out connector that are not present 
(tos, gcp).
   
   ### How was this patch tested?
   
   Manual builds; another in progress.
   
   LICENSE-binary validated by looking at dependencie of hadoop-cloud-storage, 
making sure the needed ones were there and deleting some which didn't appear 
any more. 
   
   
   ### For code changes:
   
   - [X] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [X] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> hadoop binary distribution to move cloud connectors to hadoop common/lib
> ------------------------------------------------------------------------
>
>                 Key: HADOOP-19696
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19696
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure, fs/gcs, fs/huawei, fs/s3
>    Affects Versions: 3.4.2
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>              Labels: pull-request-available
>
> Place all the cloud connector hadoop-* artifacts and dependencies into 
> hadoop/common/lib so that the stores can be directly accessed.
> * filesystem operations against abfs, s3a, gcs, etc don't need any effort 
> setting things up. 
> * Releases without the aws bundle.jar can be trivially updated by adding any 
> version of the sdk libraries to the common/lib dir. 
> This adds a lot more stuff into the distribution, so I'm doing the following 
> design
> * all hadoop-* modules in common/lib
> * minimal dependencies for hadoop-azure and hadoop-gcs (once we get those 
> right!)
> * hadoop-aws: everything except bundle.jar
> * other connectors: only included with explicit profiles.
> ASF releases will support azure out the box, the others once you add the 
> dependencies. And anyone can build their own release with everything
> One concern here, we make hadoop-cloud-storage artifact incomplete at pulling 
> in things when depended on. We may need a separate module for the distro 
> setup.
> Noticed during this that the hadoop-tos component is shaded and includes 
> stuff (httpclient5) that we need under control. Filed HADOOP-19708 and 
> incorporating here. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to