[
https://issues.apache.org/jira/browse/HADOOP-18877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765234#comment-17765234
]
Steve Loughran commented on HADOOP-18877:
-----------------------------------------
the interface here needs to be pluggable so that hboss and others trying to
mock s3 have a simple point to mock. see HBASE-28056
this means that we should make it another configuration option, just one for
wiring up in tests. maybe: add a way to set it before initialization; in init
if it has been set then don't create? we could provide both getter and setter
in S3AInternals interface.
> AWS SDK V2 - Move to S3 Java async client
> -----------------------------------------
>
> Key: HADOOP-18877
> URL: https://issues.apache.org/jira/browse/HADOOP-18877
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.0
> Reporter: Ahmar Suhail
> Assignee: Ahmar Suhail
> Priority: Major
>
> With the upgrade, S3A now has two S3 clients the Java async client and the
> Java sync client.
> Java async is required for the transfer manager.
> Java sync is used for everything else.
>
> * Move all operations to use the Java async client and remove the sync
> client.
> * Provide option to configure java async client with the CRT HTTP client.
> * Create a new interface for S3Client operations, move them out of S3AFS.
> interface will take request and span, and return response.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]