Disable XCom log for return value for KubernetesPodOperator

Open Beginner friendly
#50,892 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
data-engineering

Research direction

Start at the KubernetesPodOperator return-value XCom logging path and compare it with the PythonOperator behavior introduced in PR 19378. Done means KubernetesPodOperator provides the same ability to control return-value logging, with coverage for the changed behavior.

Written by the indexing model from the issue text.

Description

area:logging kind:feature needs-triage provider:cncf-kubernetes
Description

There was this PR that changed the xcom logging level to debug for the PythonOperator but not the KubernetesPodOperator.

It would be useful to have the same in the KubernetesPodOperators.

Use case/motivation

XComs can now get very large thus needing the ability to control if it should log or not.

Related issues

https://github.com/apache/airflow/issues/18264

Are you willing to submit a PR?
  • Yes I am willing to submit a PR!
Code of Conduct
Dominant language
Python
Stars
46.9k
Forks
17.9k
Avg merge
2d 5h
Merged PRs (30d)
480

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/airflow

All issues in apache/airflow

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.