oracle / oracle/oci-java-sdk

Multi Part size info is missing

Open
#209 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Object Storage
Dominant language
Java
Stars
243
Forks
171
Avg merge
30m
Merged PRs (30d)
4

Description

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:

  1. opc-multipart-md5 reponse header containing md5 checksum and no of parts
  2. size of the multi part being used.

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Object Storage HeadObject and CreateMultipartUpload API documentation linked in the issue, focusing on the opc-multipart-md5 and custom metadata response behavior. Determine whether multipart chunk size is exposed by the service or whether the requested offline verification needs an alternative documented process. Done means the API capability or limitation and the supported verification approach are clearly established.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.