Error message: Unable to parse ExceptionName: InvalidRequest Message: You must specify at least one part

[deekshith993]

ozone_s3g.log
be.log

While setting up an Apache Doris snapshot repository using Apache Ozone 2.2.1 as the S3-compatible object storage backend, I am encountering an issue during the repository clone/restore process.
My current environment is:
Apache Doris: 4.1.3
Apache Ozone: 2.2.1
Storage: Ozone S3 bucket
Use case: Exporting an existing Doris database as a snapshot and importing it as a clone database for UAT.

The issue occurs specifically when Doris uploads larger snapshot files to the Ozone S3 bucket. Files smaller than approximately 45 MB are uploaded successfully using a normal PutObject request. However, files larger than this threshold are uploaded using multipart upload.
The individual multipart upload parts are successfully uploaded and committed to Ozone, but the final CompleteMultipartUpload request fails with the following error:

InvalidRequest You must specify at least one part HTTP 400

As a result, the snapshot repository operation fails even though the individual multipart upload parts appear to have been successfully uploaded. I came across the following Apache Ozone JIRA issue, which appears to be very similar to the behavior I am experiencing:

https://issues.apache.org/jira/browse/HDDS-14760

From the JIRA discussion, it appears that the underlying multipart-upload issue has been fixed through an upcoming PR. However, I am unable to determine which Apache Ozone release/version contains this fix.
Could you please help confirm the following:

1. Is HDDS-14760 the same underlying issue that could cause the CompleteMultipartUpload request to fail with InvalidRequest: You must specify at least one part?
2. Has the fix for this issue already been released?
3. If it has been fixed, which Apache Ozone version contains the fix?

[jmrplens]

Yes, that's the one, and the fix isn't in any release yet.

1. HDDS-14760 is exactly this error on CompleteMultipartUpload from the AWS C++ SDK, and Doris' BE talks to S3 through that SDK (Aws::S3::S3Client in be/src/util/s3_util.cpp). Your logs show the same pattern: ozone_s3g.log has both parts of each upload as SUCCESS, and be.log shows only CompleteMultipartUpload failing. The cause, from the fix: the SDK sends CompleteMultipartUpload with Expect: 100-continue, so the body only arrives after the gateway answers 100 Continue, and Ozone's S3 gateway decided the body was empty by checking InputStream.available() == 0, which is 0 when nothing has arrived yet. That's also why only the larger files fail: the small ones never use multipart.
2. The fix is HDDS-14760. Fix CompleteMultipartUpload rejecting chunked request body as empty #10461 (commit f5f2e14), merged into master on 2026-07-02. It is not in 2.2.0 or 2.2.1: both come from the ozone-2.2 branch, which doesn't have it (and neither does 2.1.2).
3. The first release with it will be the next one cut from master, currently 2.3.0-SNAPSHOT. The JIRA has no Fix Version set, and ozone-2.2 is already at 2.2.2-SNAPSHOT, so asking on the JIRA for a backport now could get it into 2.2.2. The change itself is ten lines in one class of the S3 gateway (CompleteMultipartUploadRequestUnmarshaller), and that file is the same in 2.2.1 as in the commit the fix was made on, so it applies cleanly if you'd rather patch 2.2.1 yourself in the meantime.

[deekshith993]

@jmrplens,
Thank you for the details, it means a lot.
I'll try to do the patch and check.