Multipart uploads provide efficient and resilient uploads, especially for large objects. Multipart uploads also accommodate
objects that are too large for a single upload operation. With multipart uploads, individual parts of an object can be
uploaded in parallel to reduce the amount of time you spend uploading. Multipart uploads can also minimize the impact
of network failures by letting you retry a failed part upload instead of requiring you to retry an entire object upload.
See [Managing Multipart Uploads](https://docs.us-phoenix-1.oraclecloud.com/Content/Object/Tasks/managingmultipartuploads.htm).
To use any of the API operations, you must be authorized in an IAM policy. If you're not authorized,
talk to an administrator. If you're an administrator who needs to write policies to give users access, see
[Getting Started with Policies](https://docs.us-phoenix-1.oraclecloud.com/Content/Identity/Concepts/policygetstarted.htm).
Note: Objects should always be created or deserialized using the
Builder. This model distinguishes fields
that are
null because they are unset from fields that are explicitly set to
null. This is done in
the setter methods of the
Builder, which maintain a set of all explicitly set fields called
#__explicitlySet__. The
#hashCode() and
#equals(Object) methods are implemented to take
#__explicitlySet__ into account. The constructor, on the other hand, does not set
#__explicitlySet__(since the constructor cannot distinguish explicit
null from unset
null).