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 2019/12/03 16:21:00 UTC
[jira] [Updated] (HADOOP-16742) Possible NPE in S3A
MultiObjectDeleteSupport error handling
[ https://issues.apache.org/jira/browse/HADOOP-16742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-16742:
------------------------------------
Summary: Possible NPE in S3A MultiObjectDeleteSupport error handling (was: Possible NPE in S3A aliveMultiObjectDeleteSupport error handling)
> Possible NPE in S3A MultiObjectDeleteSupport error handling
> -----------------------------------------------------------
>
> Key: HADOOP-16742
> URL: https://issues.apache.org/jira/browse/HADOOP-16742
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Environment: non-AWS S3 endpoint/mock endpoint
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
>
> Reported in a github PR https://github.com/apache/hadoop/pull/1688 by Tor Arvid Lund
> bq. I've hit an issue where a DeleteObjects request using LocalStack causes a NullPointerException in the translateDeleteException function. error.getCode() can return null, and if there is more than one error returned by deleteException.getErrors(), this will cause the NPE.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org