Details
-
Bug Report
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
Description
Problem:
If the engine history contains more entities (activityInstances, variable updates etc.) with the exact same timestamp (same milliseconds) than the currently configured maxPage size for that particular entity (see *.maxPageSize properties https://docs.camunda.org/optimize/latest/technical-guide/setup/configuration/#engine-common-settings ). The Optimize import will miss some of these entities as the "same timestamp as last entity" step of the import will not catch more than the maxPageSize entities.
Steps to reproduce:
1. Make sure that more than the maxPageSize of a particular entity import entities exist in the cambpm history. (e.g. variable updates).
2. run the Optimize import and let it finish
3. compare the expected and actual counts of the particular entity
Actual result :
Optimize contains less entities than expected
Expected result:
All data is imported as expected, regardless of timestamp distribution
Hint:
Addressing the root cause will likely require adjustments to the Camunda BPM Optimize rest api.