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

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

steveloughran commented on PR #7980:
URL: https://github.com/apache/hadoop/pull/7980#issuecomment-3312222391

   did you do a `mvn clean package`?
   
   
`hadoop-cloud-storage-project/hadoop-cloud-storage/target/hadoop-cloud-storage-3.5.0-SNAPSHOT/share/hadoop/common/lib`
  -new, contains all cloud stuff we want in; should cut stuff already going to 
be there just to reduce copying
   
   `hadoop-dist/target/hadoop-3.5.0-SNAPSHOT/share/hadoop/tools/lib`
   should remove hadoop-azure, hadoop-aws, hadoop-gcs, bundle.jar...
   
   the big distro created under `hadoop-dist/target/hadoop-3.5.0-SNAPSHOT/` is 
what is shipped.
   




> 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 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