control-service: add logging when updating last execution #657
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We got reports that the last execution status of a data job can get out-of-sync with the status persisted in the data_job_execution table. This commit adds logging to the method that updates the last execution information of a data job so that it is easier to troubleshoot. Testing done: unit tests Signed-off-by: Tsvetomir Palashki <[email protected]>
tpalashki
force-pushed
the
person/tpalashki/control-service
branch
from
10c6d71 to
ec5ad4e
Compare
doks5
approved these changes
Dec 23, 2021
.../projects/pipelines_control_service/src/main/java/com/vmware/taurus/service/JobsService.java
Show resolved
Hide resolved
.../projects/pipelines_control_service/src/main/java/com/vmware/taurus/service/JobsService.java
Show resolved
Hide resolved
mivanov1988
approved these changes
Jan 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We got reports that the last execution status of a data job
can get out-of-sync with the status persisted in the data_job_execution
table. This commit adds logging to the method that updates the last
execution information of a data job so that it is easier to troubleshoot.
Testing done: unit tests
Signed-off-by: Tsvetomir Palashki [email protected]