-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
CAM-14006: avoid job log query on incident creation #1665
Conversation
I'll squash the commits after the review to avoid retriggering the CI for now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good to me 👍
Great that we have a migration test as well 👍
There is one import we can probably remove from one class, but that's it.
Edit: do we need to handle the same issue for the ExternalTaskEntity#getFailureLogId
?
engine/src/main/java/org/camunda/bpm/engine/impl/persistence/entity/JobEntity.java
Show resolved
Hide resolved
- the job log reference is needed as the incident's history configuration - the query can be expensive; so instead of trying to find the matching job log later, we carry the reference forward in the job and then to the incident when it is created related to CAM-14006
- makes this behavior consistent with how it is implemented for jobs related to CAM-14006
b51a4db
to
1741ca4
Compare
I have extended the solution to external tasks and removed the unnecessary import. Please re-review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks all good with regards to the External Task extension. 👍
We need to fix the CockroachDB upgrade script, however.
Feel free to merge after that.
related to CAM-14006