Storing an object or version of an object

You use the HTTP PUT method to store an object or new version of an existing object in a namespace. You can optionally use this method to store the object or version data and custom metadata in a single operation.

To store versions, the namespace must be configured to allow versioning. When versioning is enabled, storing an object with the same name as an existing object creates a new version of the object.

You can store new versions of any object, including multipart objects created by using the multipart upload feature of the S3 compatible API, as long as the object is not under retention or on hold. You cannot store new versions of an object that is under retention or on hold.

By default, a new object inherits several metadata values from namespace configuration settings. A new version of an object inherits the metadata values of the previous version of the object. However, in either case, you can override this default metadata when you store the object or version. For more information about this, see Specifying metadata on object creation.

Tip: To store very large objects, use the S3 compatible API. With the S3 compatible API, you can break the data for an object into multiple parts and upload the parts to HCP individually. The process of creating an object by uploading the data in parts is called multipart upload. The result of a multipart upload is a single object that behaves in the same way as objects for which all the data was stored by means of a single PUT object request.

For more information about multipart uploads, see Working with multipart uploads.

© 2015, 2020 Hitachi Vantara LLC. All rights reserved.