-
Notifications
You must be signed in to change notification settings - Fork 569
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail to export the process instance modification record to Elasticsearch #10732
Comments
If we're now exporting everything, please update integration tests to test for all records - when we initially implemented it, we excluded some value types since not everything was exported to ES at the time. |
This apparently didn't catch this problem. Modification records are part of the list that's returned here. |
Then my guess is it's with the protocol factory which does not generate the record in a way to trigger the bug =/ Here's the generated record which is successfully exported:
|
Ah, activatedElementInstanceKeys is not part of the API. If it's not part of the API, should it be exported, or should it be ignored in the template (but maybe part of the source)? |
I agree, ignoring it makes sense. It's only used internally |
On thing we could do to keep serialization on par with the API, is instead of using |
Describe the bug
Since version
8.1.1
, we can't export the process instance modification record to Elasticsearch anymore. This is a regression to the previous version8.1.0
.In bug fix #10609, we updated the record. But we forgot to update the ES template.
If a process instance modification is applied then the ES exporter tries to export the record and fails. As a result, no other records can be exported anymore.
To Reproduce
Expected behavior
The ES exporter can export process instance modification records.
Log/Stacktrace
Full Stacktrace
Environment:
8.1.1
The text was updated successfully, but these errors were encountered: