![]() |
Spectra Logic |
1-800-833-1132 : 1-303-449-6400 |
Create a job to stream PUT object requests. Clients should use this before putting objects to physical data stores. See Processing a Bulk PUT Job for an overview of the process.When this request is issued, an idle timer starts and the reservation expires after 24 hours elapse. The timer is reset by performing an IO operation (such as a `PUT Object` operation) or by issuing a Modify Job request (see Modify Job), even if you do not modify anything.
PUT http[s]://{datapathDNSname}/_rest_/bucket/{bucket UUID or name}?operation=START_BULK_PUT[&aggregating=TRUE|FALSE][&force][&ignore_naming_conflicts][&implicit_job_id_resolution=TRUE|FALSE][&max_upload_size={64‑bit integer}][&minimize_spanning_across_media=TRUE|FALSE][&name={string}][&priority=URGENT|HIGH|NORMAL|LOW]<Objects
WriteOptimization="CAPACITY|PERFORMANCE">
<Object Name="{string}" Length="{64‑bit integer}"/>
<Object Name="{string}" Length="{64‑bit integer}"/>
</Objects>
Specifies whether job chunks are written as quickly as possible or across as few pieces of media as possible. When CAPACITY mode is used for writing to tape, job chunks are written concurrently to multiple tapes using multiple drives if the tapes being written to are already assigned to the bucket, or there is so much data to write that the system knows multiple tapes are needed to write all of the data. When in PERFORMANCE mode, job chunks are written as quickly as possible, even if that means that more tapes are allocated to the bucket than are necessary to write the data.It is better to use CAPACITY mode if the tapes will be ejected after the job completes or if the bucket is written to very rarely and capacity in the library is of concern. PERFORMANCE mode is recommended in all other cases.Pools should generally have a CAPACITY write optimization since pools are very fast and under less contention. It is rare for a pool storage domain to benefit from a PERFORMANCE write optimization.Values: CAPACITY, PERFORMANCE Note: Object_names must follow the Amazon S3 naming restrictions. See Object Key and Metadata for more information. <MasterObjectList
Aggregating="TRUE|FALSE"
BucketName="{string}"
CachedSizeInBytes="{64‑bit integer}"
ChunkClientProcessingOrderGuarantee="IN_ORDER|NONE"
CompletedSizeInBytes="{64‑bit integer}"
EntirelyInCache="TRUE|FALSE"
JobId="{string}"
Naked="TRUE|FALSE"
Name="{string}"
OriginalSizeInBytes="{64‑bit integer}"
Priority="CRITICAL|URGENT|HIGH|NORMAL|LOW|BACKGROUND"
RequestType="PUT"
StartDate="YYYY-MM-DDThh:mm:ss.xxxZ"
Status="IN_PROGRESS|COMPLETED|CANCELED"
UserId="{string}"
UserName="{string}">
<Nodes>
<Node EndPoint="{string}" Id="{string}"/>
</Nodes>
<Objects
ChunkId="{string}"
ChunkNumber="{32‑bit integer}">
<Object Id="{string}" InCache="TRUE|FALSE"
Latest="TRUE|FALSE" Length="{64‑bit integer}"
Name="{string}" Offset="{64‑bit integer}"
Version="{64‑bit integer}"/>
...
</Objects>
...
</MasterObjectList>
Whether the job can have additional PUTs or GETs appended to it. Jobs aggregate if created with the aggregating request parameter set to TRUE, or if created by the BlackPearl system in response to Amazon S3 PUT and GET requests. Values: TRUE, FALSE The amount of data that has been transferred to the cache for this job. For RequestType=PUT, this is the amount of data successfully transferred to the BlackPearl Converged Storage System from the client. The amount of data that is completely processed for this job. For RequestType=PUT, this indicates the amount of data written to all permanent data stores. Whether the job was created as the result of a native S3 command (TRUE) or a Create Bulk GET/PUT/VERIFY job command (FALSE). Values: TRUE, FALSE The priority for processing this job. The job priority determines the assigned resources and processing order. Values: CRITICAL, URGENT, HIGH, NORMAL, LOW, BACKGROUND The date and time the job was started in the format YYYY-MM-DDThh:mm:ss.xxxZ.
§ IN_PROGRESS — The job is currently running.
§ COMPLETED — The job completed.
§ CANCELED — The job was canceled by the user or automatically due to internal timeouts. PUT http://blackpearl-hostname/_rest_/bucket/bucket1 ?operation=start_bulk_put&name="PutJob" HTTP/1.1