[flyin] Use current context logger instead of root logger to show info level logs #1998
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.
Tracking issue
flyteorg/flyte#4284
Why?
Originally, we used the root logger imported from flytekit. However, it doesn't show the info level logs. The default level is a warning.
What?
Switch to use the logger from flytekit current_context, which is used to print logs during execution. By default, it uses user-space logger, whose level is INFO, so it can also print logs >= INFO level.
The usage is simple. We call
logger = flytekit.current_context().logging
to get the logger.Test