Introduction
Batches were introduced in 20.2 to easily and safely operate on a large amount of data. Batches operate on a large data set of records conveyed via a filter. The data set is then linked to one of the various tasks. Batches can either be started manually in the MediaHaven REST API or created by a workflow process.
Error Handling
Batches will handle every record matching the provided query. Depending on the outcome of the handling the following properties of the batch change
The record did change → Completed increments by 1
The record did not change → Skipped increments by 1
Failure → Failed increments by 1
The batch does not abort on failure but keeps on processing the subsequent records.
API Permissions
POST batches/
Any user can create batches for the index of their own organisation; the created batches search as the user who created to batch.
GET batches/
The returned batches depend on the function of the user
Function | Effect |
|---|---|
No | Can read the batches created by this user |
| Can read all the batches from the index of the organisation of this user |
| Can read all batches from all indices |
Multi indices 22.2+
Normally, a batch is executed on the index of the organization to which the user belongs. When a batch is started by the zeticon@installation or system@installation user, it will be executed across all indices available on the system.