HCP Tenant Management Help
The DELETE request to delete an object has these elements:
•If you’re accessing the namespace as an authenticated user, an Authorization header
•The URL of the object or symbolic link
To perform a privileged delete, the request must specify both of these URL query parameters:
privileged=true
reason=reason-text
reason-text must be from one through 1,024 characters long and can contain any valid UTF-8 characters, including white space.
You can specify the parameters in either of these ways:
•As query parameters at the end of the URL, in this format:
?privileged=true&reason=reason-text
•As form-encoded data (application/x-www-form-urlencoded content type) in the request. For example, in cURL, you can use the -d option to specify form-encoded data in a DELETE request.
These considerations apply:
•If you use query parameters, you need to percent-encode characters in the reason parameter that have special meanings in URLs. For more information about percent-encoding, see URL considerations.
•If you use form-encoded data, you need to percent-encode only ampersands (&) in the reason parameter. This prevents HCP from interpreting these characters as starting a new URL query parameter.
•You cannot combine query parameters and form-encoded data in a single request.
Deleting a specific version by version ID
To delete a specific version of an object, the request must specify this URL query parameter:
version=version-id
To find the ID of the version you want, list the versions of the object. For more information about listing the versions of an object, see Listing object versions.
Deleting a version by timestamp
To delete a specific version of an object at a specified time, the request must specify this URL query parameter:
version=create-time-milliseconds
To find the ingest time of the version you want, list the versions of the object. For more information about listing the versions of an object, see Listing object versions.
You can also use a GET request to retrieve the timestamp or timestamp range of an object, which you can use to find a version of that object.
Deleting a range of versions using version IDs
To delete a range of versions of an object, specify the version URL query parameter with the range of object version IDs you want to delete. You can omit this parameter to delete the current version of an object.
To find the ID of the versions you want, by list the versions of the object, as described in Listing object versions.
The version query parameter has this format:
?version=<StartVersionID>-<EndVersionID>
The table below shows the way in which you can specify the range.
Range specification | Description | Example |
---|---|---|
StartVersionID–End-VersionID |
VersionID in StartVersionID through EndVersionID, inclusive. |
Object versions beginning with 91728994268353 through object version 91728994618369: 91728994268354-91728994618369 |
These rules apply to the version query parameter:
•If you omit the parameter, HCP deletes the current version of an object.
•If you specify a valid range, HCP deletes the requested amount of data with a status code of 200.
Deleting a range of versions using timestamps
To delete a range of versions of an object using the version ingest timestamps, specify the version URL query parameter with the range of object timestamps you want. You can omit this parameter to delete the current version of an object.
To find the ingest timestamps of the versions you want, by listing the ingest timestamps of the versions, see Listing object versions.
The version query parameter with create timestamp range has this format:
?version=@start-Create-Time-Milliseconds-@end-Create-Time-Milliseconds
The table below shows the way in which you can specify the range.
Range specification | Description | Example |
---|---|---|
@start-Create-Time-Milliseconds– |
Version timestamp in start-Create-Time-Milliseconds, exclusive, through –end-Create-Time-Milliseconds, inclusive |
Object versions beginning at ingest timestamp 1493911519817 through ingest timestamp 1493911519820: @1493911519817–@1493911519820 |
These rules apply to the version ingest timestamp range query parameter:
•If you omit the parameter, HCP deletes the current version of an object.
•If you specify a valid range, HCP deletes the requested amount of data with a status code of 200.
Trademarks and Legal Disclaimer
© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.