Refactor loggers to allow for different output paths #59
Conversation
This file contains hidden or 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
- Now each logger can have a different output path, but we are only
using one output path. This is to allow for logging to different dirs
depending on the current run, without having to kill the pipeline (this
is for go-seek mainly).
- Remove log_output gflag and use instead the `log_output_path` yaml parameter
in PipelineParams.yaml. If this parameter is empty "" then no logging is done
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.
using one output path. This is to allow for logging to different dirs
depending on the current run, without having to kill the pipeline (this
is for go-seek mainly).
log_output_pathyaml parameterin PipelineParams.yaml. If this parameter is empty "" then no logging is done