[BEAM-14011] AWS SDK2 S3FileSystem MultiPart Copy sets incorrect request parameters

• Type: Bug
• Status: Triage Needed
• Priority: P2
• Resolution: Fixed
• Affects Version/s: 2.29.0, 2.30.0, 2.31.0, 2.32.0, 2.33.0, 2.34.0, 2.35.0, 2.36.0
• Fix Version/s: 2.38.0
• Component/s: io-java-aws
• Assignee: Stephen Patel
• Reporter: Stephen Patel
• Created: 28/Feb/22 20:45
• Updated: 13/Apr/23 11:09
• Resolved: 04/Mar/22 16:26

Description

The following code locations use incorrect parameters:
Here and Here specifies the sourcePath instead of the destinationPath.

Here specifies destinationPath.getBucket() instead of sourcePath.getBucket()

Here specifies a constant part number of 1, instead of using the partNumber variable.

Taken together, these issues cause multipart copies to fail due to:

software.amazon.awssdk.services.s3.model.NoSuchUploadException: The specified upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed.

If the object references are fixes, the part number issue causes multipart copies to fail due to:

software.amazon.awssdk.services.s3.model.S3Exception: The list of parts was not in ascending order. Parts must be ordered by part number. 

Note: I checked the AWS SDK1 S3FileSystem and did not see the same issues.

Issue Links

• links to: GitHub Pull Request #16987