refactor: use JobProgress tracking in data value import [DHIS2-18885] #19781
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.
Summary
This started as a cleanup PR for Notifier stuff but I found that the ADX import multi-threading solution messed up the notification messages as messages from different threads were writing into the same notification list. Looking into that I ended up removing the cause of the problem by streamlining the ADX data value import.
JobProgress#setWorkItemBucketing
to prevent too many items by "merging" n items into one "bucket" itemAutomatic Testing
Existing tests were adjusted.
Manual Testing