Incorrect behavior on CompleteMultipartUpload when some parts are unused #198

New issue

Closed

opened 2022-01-19 20:45:25 +00:00 by trinity-1686a · 2 comments

trinity-1686a commented

2022-01-19 20:45:25 +00:00

Owner

I haven't tested it, but looking at the code, we currently reject CompleteMultipartUpload where some parts were uploaded but not used. AWS allow this behavior, and presumably delete unused parts

trinity-1686a added the

scope

s3-api

label 2022-01-19 20:45:25 +00:00

trinity-1686a added the

prio

low

label 2022-01-20 15:17:25 +00:00

lx commented

2022-01-25 11:15:22 +00:00

Owner

Currently the data model can't handle this, since once a block/part has been added to the Version, it cannot be removed, and also numbering changes are not supported.

Apparently AWS S3 renumbers parts on CompleteMultipartUpload. For instance if we complete a multipart upload taking parts 2, 3, 5, 9, then these parts can be obtained respectively with `partNumber=1`, `2`, `3`, `4` in for instance HeadObject or GetObject. Currently the data model can't handle this, since once a block/part has been added to the Version, it cannot be removed, and also numbering changes are not supported.