Steve Loughran created HADOOP-19592:
---------------------------------------
Summary: S3A: S3 Express bucket failure of conditional overwrite
of multiparts is 200 + error, not 412
Key: HADOOP-19592
URL: https://issues.apache.org/jira/browse/HADOOP-19592
Project: Hadoop Common
Issue Type: Bug
Components: fs/s3
Affects Versions: 3.4.2
Reporter: Steve Loughran
The S3 Express response to create conflicts of multipart uploads is not a
412/419, it is 200 + an xml error.
{code}
Error
Code: PreconditionFailed
Message: At least one of the pre-conditions you specified did not hold
Condition: If-None-Match
RequestId: 01e17cb4f5000197899662aa050968218250cedb
HostId: K1OApth
{code}
This is raised an exception in the SDK, but it isn't mapping to a 419/412, the
way we expect, so is mapped to
a generic AWSS3IOException.
{code}
AWSS3IOException: Completing multipart upload on
test/testIfNoneMatchConflictOnMultipartUpload:
software.amazon.awssdk.services.s3.model.S3Exception: At least one of the
pre-conditions you specified did not hold (Service: S3, Status Code: 200,
Request ID: 0110480881000197899bc814050902966399617b, Extended Request ID:
y1E4oDawYBQ7XsAVFA):PreconditionFailed: At least one of the pre-conditions you
specified did not hold (Service: S3, Status Code: 200, Request ID:
0110480881000197899bc814050902966399617b, Extended Request ID:
y1E4oDawYBQ7XsAVFA)
{code}
If this is expected behaviour of S3 express:
* docs need updating
* unless it is on the SDK roadmap, we should catch and map to condition
failures, presumably RemoteFileChangedException,
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]