This offer is only addressed to commercial customers including freelancers and entrepreneurs. All prices are exclusive of value added tax (VAT).
  • Share via email
  • Subscribe to blog alert

Reprocessing Job API | Backward incompatible changes

Reprocessing Job API used instanceCount property to define the number of instances for a reprocessing job. A new deploymentSettings property has been introduced to define the number of instances, memory, and storage settings for a reprocessing job.

Breaking changes 

  • Start a new reprocessing job(s) endpoint does not accept instanceCount anymore. Now, the property is named deploymentSettings
  • Retrieve all reprocessing jobs endpoint does not provide instanceCount anymore. Now, the property is named deploymentSettings
  • Retrieve a reprocessing job endpoint does not provide instanceCount anymore. Now, the property is named deploymentSettings

Default values

For the instances in deploymentSettings property, the default value is 1.

For memory and storage, the default values are provided by the pipeline.

"deploymentSettings": {

   "instances": 1,

 "memory": 0,

"storage": 0

}

As a result, the following endpoints are affected:

  • /v2/{project}/pipeline/reprocessingJobs. For details, refer to Swagger U .
  • /v2/{project}/pipeline/reprocessingJobs. For details, refer to Swagger UI.
  • /v2/{project}/pipeline/reprocessingJobs/{id}. For details, refer to Swagger UI.

The changes allow you define your own RAM and storage settings and change the default value of the number of instances. Find the reprocessing steps for updating these settings in the Reprocessing the input history user guide.