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 2022/06/10 14:17:00 UTC

[jira] [Commented] (HADOOP-18286) S3a: allow custom retry policies

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

Steve Loughran commented on HADOOP-18286:
-----------------------------------------

That would be okay provided the plug-in point is tagged as @unstable; name a class which takes Configuration as its parameter.

There is some discussion underway about moving to the aws 2.x SDK, I am though I'm not in the next feature release. That may add complications here, as well as for extension points for signing and credentials provision.

> S3a: allow custom retry policies
> --------------------------------
>
>                 Key: HADOOP-18286
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18286
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 3.3.3
>            Reporter: André Kelpe
>            Priority: Major
>
> This is related to HADOOP-18285
> It would be great if the retry policies were pluggable so that one could inject their own implementation to overcome exceptional cases not correctly covered by the current policy. Currently {color:#24292f}S3ARetryPolicy{color} is hard-wired and can not be replaced w/o heavy sub-classing gymnastics.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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