fix(s3_task_handler.py): upload log with put_object#68619
Merged
Conversation
Signed-off-by: PoAn Yang <payang@apache.org>
boring-cyborg
Bot
added
area:logging
area:providers
provider:amazon
1 task
vincbeck
approved these changes
Jun 16, 2026
RulerChen
pushed a commit
to RulerChen/airflow
that referenced
this pull request
Jun 16, 2026
When S3 is configured as the remote log backend, task log files are incorrectly reported as task outputs in OpenLineage events. Upload the log via the boto3 client directly (get_conn().put_object(...)) instead of S3Hook.load_string(), so the log write never touches the hook lineage collector.
75 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When S3 is configured as the remote log backend, task log files are incorrectly reported as task outputs in OpenLineage events.
Upload the log via the boto3 client directly (
get_conn().put_object(...)) instead ofS3Hook.load_string(), so the log write never touches the hook lineage collector.closes: #68585
Was generative AI tooling used to co-author this PR?
Generated-by: [Claude Code with Opus 4.8] following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.