Loading Bulk Specification After State Recovery
Following properties were introduced to control from where the bulk specification would be loaded when creating a new single or recurring bulk when a state of given behaviour is recovered/rehydrated:
ipf.bulker {
aggregate {
read-specification-from-context {
single-bulk = false
recurring-bulk = false
}
}
}These 2 properties are used to control if the specification will be taken out of the state or from the configuration properties(hocon). The motivation behind introducing this feature was that the changes in bulker configuration(hocon) did not get reflected after re-deployment(restart) of the application. New configs were not updated due to bulk identification, so old configs were still being picked up from durableStateEntity table with the persistence id (icf+instructing agent).
In order to resolve this issue, these 2 properties were introduced to allow the client to decide if the config should be applied directly from the config file or the parent component bulk specification should be applied.
|
Note that this feature must be used with caution. Not all bulk specification properties should be changed as this could
cause issues with the existing bulk instances.
For example, |