[BUG] Map task logging level fixed at 30 for default logger #3032
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
closes flyteorg/flyte#5961
fixes: https://linear.app/unionai/issue/DX-1155/investigate-logging-level-behavior-in-map-tasks
Why are the changes needed?
Logging for map tasks always defaults to default since logging library is re-imported in array node map task after being initialized in the wf code's files
What changes were proposed in this pull request?
remove logging import and utilize flytekit logger instead
How was this patch tested?
built an image w/ the changes and ran:
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link
Summary by Bito
Fixed a logging level inconsistency in map tasks by removing direct logging import in array_node_map_task.py and implementing flytekit logger instead. This ensures logging levels are properly inherited between workflow code and map tasks, resolving the issue where map tasks were fixed at level 30.Unit tests added: False
Estimated effort to review (1-5, lower is better): 1