[
https://issues.apache.org/jira/browse/HADOOP-18708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855572#comment-17855572
]
ASF GitHub Bot commented on HADOOP-18708:
-----------------------------------------
steveloughran commented on PR #6884:
URL: https://github.com/apache/hadoop/pull/6884#issuecomment-2172927119
It's still happening in FileSystem.initialize().
If I get time this week I'll do my PoC of lazy creation of transfer manager
and async client, as that's doubled startup time already. all of that will be
moved behind S3Store with only the copy() methods exposed.
Ultimately I want the S3Client itself hidden behind that API, so here
* new unencryptedS3 operations `getLengthOfEncryptedObject(path)`, ...,
would trigger demand creation of the method
* accessor to this passed down.
Actually, `createFileStatusFromListingEntry()` could be part of S3AStore
took, somehow. all the config information for the creation, especially cSE
flags, would be in the store config, so listing wouldn't need it
> AWS SDK V2 - Implement CSE
> --------------------------
>
> Key: HADOOP-18708
> URL: https://issues.apache.org/jira/browse/HADOOP-18708
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.0
> Reporter: Ahmar Suhail
> Assignee: Syed Shameerur Rahman
> Priority: Major
> Labels: pull-request-available
>
> S3 Encryption client for SDK V2 is now available, so add client side
> encryption back in.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
