Details
-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
Description
Brief summary of the bug. What is it ? Where is it ?
During import of zeebe process instance records, we get the record type and check that it is a type that we import (don't ignore). However, if this type is null, then we get an NPE because the ignorable types set is checking for whether or not a null entry is contained.
In the worst case scenario, this blocks the import of any future process instance records as Optimize cannot get past this point.
Note that this was only seen with a single cluster using an alpha version, so it might be that they have deployed a process containing an element that was at the time not supported.
Steps to reproduce:
In this case, the following scenario happened:
- using 3.10.0-alpha5 Optimize
- deploy a process containing a zeebe element with no type specified
- observe the Optimize importer
Actual result:
Zeebe importer gets stuck and no new process instance record data is imported
Expected result:
Optimize ignores data for records that it cannot process
Notes:
This fix should be backported to older maintenance branches