Disable XCom log for return value for KubernetesPodOperator
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
### Description
There was this [PR](https://github.com/apache/airflow/pull/19378) 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?
- [x] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
Contributor guide
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.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100