[
https://issues.apache.org/jira/browse/HADOOP-15226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932267#comment-16932267
]
Steve Loughran commented on HADOOP-15226:
-----------------------------------------
Not really, no. I did a backport the critical off-by-one seek bug all the way
to branch-2.8.
We have been thinking about back porting AWS SDK updates, and that would
include adding awareness of PAYG DDB tables, maybe even default to creating
them. I like to keep costs down.
Other than that -is there any critical patch which you think needs to be pulled
back? The DDB throttling resilience is one you could point at -but with
on-demand tables that throttling never seems to surface.
> Über-JIRA: S3Guard Phase III: Hadoop 3.2 features
> -------------------------------------------------
>
> Key: HADOOP-15226
> URL: https://issues.apache.org/jira/browse/HADOOP-15226
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3
> Affects Versions: 3.0.0, 3.1.0
> Reporter: Steve Loughran
> Priority: Major
> Fix For: 3.2.0
>
>
> S3Guard features/improvements/fixes for Hadoop 3.2
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
