Create Job
This is the interface used by the data management service to instantiate a job, do not use directly.
The job information. The format is made up of several fields required by R1 data management, plus an info_job_data field that is specific to the type of job being created. In this case a cmread, cmwrite, or cmtrack job.
{
"owner": "string",
"last_updated": "string",
"info_job_identity": "94ec9a62-213b-11ec-af33-7f567fdd0e71",
"target_uri": "http://consumer:8080/v0alpha1/jobs_results/94ec9a62-213b-11ec-af33-7f567fdd0e71",
"info_type_identity": "cmwrite",
"status": 0
}The owner of the job, usually the name of rApp that created the job.
The time when the job was last updated or created (ISO-8601).
The identifier for the job, usually a UUID.
URI to which the produced information is sent. This can be actual results, or in the case of cmwrite a notification of where to retrieve the results.
info_job_data
Identifier of the data or information type used for the job.
An integer value representing the status of the job.
An empty response indicating the job was successfully created. It will be processed asynchronously.
The request is of the correct content-type but is incorrectly formed in some fashion: missing required fields, using wrong types for valid fields, or not capable of being processed as the expected input.
{
"type": "string",
"title": "string",
"status": 400,
"detail": "Required field 'counter_names' missing.",
"instance": "string"
}A URI representing the type of the problem.
A short summary of the error.
The HTTP Response code associated with this error.
A detailed description of the error.
An optional URI of the instance involved in the problem.