tsammut
commented
4 years ago Hi @aaraodeo, thank you for the question. We do not currently expose the part sizes used during a multipart upload. We've captured it as an enhancement request and will consider it in the future.
OCI API version used: 20160918
As mentioned in https://docs.cloud.oracle.com/en-us/iaas/api/#/en/objectstorage/20160918/Object/HeadObject rest request api documentation, the response obtained contains "opc-multipart-md5" header which has md5 checksum of the object stored in object storage. Also it contains the info about no of multi parts being used to construct the object in oci object storage back end using multi part upload. But what is the multipart size (chunk size in bytes) being used is not revealed as part of the response.
If we want to verify the integrity of the object stored in oci object storage backend in offline after downloading the object from OCI object storage backend we need following info:
But no info is revealed about the size of multipart being used as part of multi part upload process as part of HeadObject Response.
We tried adding a custom meta header like "opc-meta-multipartsize":"50" as request header as part of https://docs.cloud.oracle.com/en-us/iaas/api/#/en/objectstorage/20160918/MultipartUpload/CreateMultipartUpload request, expecting the header will be available as response header as part of the HeadObject request response, but its not working.
Kindly expose the info about the multipart size (in bytes) being used internally for multipart upload ,so that we can verify the md5 checksum of the object in offline.
Also kindly provide info if we can verify the checksum of the object using an alternative process.