Create Job
This is the interface used solely by data management (DMS) to instantiate a job.
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 data-type of the job being created. In this case a pmhistory job.
{
"owner": "energy-saving",
"last_updated": "string",
"info_job_identity": "94ec9a62-213b-11ec-af33-7f567fdd0e71",
"target_uri": "http://pmhistory-consumer:8080/v0alpha1/jobs_results/94ec9a62-213b-11ec-af33-7f567fdd0e71",
"info_job_data": {
"start": 1632781620000,
"end": 1632929865000,
"technology": "string",
"cell_ids": [
"3139998247308295"
],
"counter_names": [
"PMUECTXTSETUPATT"
]
},
"info_type_identity": "pmhistory"
}The identifier for the rApp that made the job request.
The time when the job was last updated or created (ISO-8601)
The unique identifier for the job provided in the job request. A uuid.
URI to which the produced information is sent. This can be actual results, or in the case of pmhistory a notification of where to retrieve the results.
Identitifer of the data or information type used for the job.
The job was successfully created.
{
"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.