Use run number generated by harvester when determining what files to process #60
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
jonescc
changed the title
|
Ready for review/merge. |
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.
The harvesting components were using the last_run_no from index_job to lookup files that needed to be processed which caused problems when more than one invocation of the harvester could be run at once (i.e. the generic_timestep harvester). Instead record the run_number generated by the harvester in a global map and use it when looking for files that need to be processed so the right ones are selected.
Moved common javajet code to harvesting component templates to reduce duplication.
Resolves the issue locally for me.