Loading...

XML

Word

Printable

Removal time is calculated based on the engine's configuration settings for the removal time strategy (start, end, none) and the TTL of the batch:
```
Batch batch = historyService.setRemovalTimeToHistoricBatchesAsync()
      .byQuery(query)
      .calculatedRemovalTime()
      .executeAsync();
```
- if removal time strategy is set to ...
  - start: removal time = start time + TTL
  - end: removal time = end time + TTL
  - none: no update is performed
Removal time can be set to an absolute value or to null:
```
Batch batch = historyService.setRemovalTimeToHistoricBatchesAsync()
      .byQuery(query)
      .absoluteRemovalTime(new Date())
      .executeAsync();
```
- the engine's configuration settings in terms of the removal time strategy (start, end, none) are disrespected
Throw BadUserRequestException if ...
- no historic batch can be found
- no mode (i. e. calculatedRemovalTime / absoluteRemovalTime) was selected
- no query was defined

is related to

CAM-10172 Introduce extra mysql queries for setting removal time async without respecting hierarchies

CAM-10246 For byte arrays related to job logs produced by batches no removal time is present

CAM-10249 Removal time is not cleared by calculation

CAM-10224 I can set a removal time by instance ids via batch asyncronously

CAM-10173 Introduce specific create auth permission for all removal time batches

CAM-10174 Introduce operation logs for all removal time batches

CAM-10175 I can read documentation about removal time batches

CAM-10176 Using REST API, I can set a removal time via batches asyncronously

CAM-9967 History data created with versions < 7.10.0 are not removed by removal-time-based strategy

(4 is related to)