You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2019/06/24 22:35:00 UTC
[jira] [Resolved] (HADOOP-16363) S3Guard DDB store prune() doesn't
translate AWS exceptions to IOEs
[ https://issues.apache.org/jira/browse/HADOOP-16363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-16363.
-------------------------------------
Resolution: Fixed
Fix Version/s: 3.3.0
Fixed in the HADOOP-15183 patch
> S3Guard DDB store prune() doesn't translate AWS exceptions to IOEs
> ------------------------------------------------------------------
>
> Key: HADOOP-16363
> URL: https://issues.apache.org/jira/browse/HADOOP-16363
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.2.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 3.3.0
>
>
> Fixing in HADOOP-15183: if you call prune() against a nonexist DDB table, the exception isn't being translated into an IOE.
> This is interesting as the codepath is going through retry(), it's just that where the IO is taking place is happening inside the iterator, and we don't have checks there.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org