You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/11/18 04:01:26 UTC

[GitHub] [airflow] uranusjr opened a new issue #19670: Configure return value logging for a DecoratedOperator

uranusjr opened a new issue #19670:
URL: https://github.com/apache/airflow/issues/19670


   ### Body
   
   Continuation of #19378
   
   https://github.com/apache/airflow/pull/19378#issuecomment-966898703
   > If the user uses `DecoratedOperator` as shown below through [TaskFlow API](https://airflow.apache.org/docs/apache-airflow/stable/tutorial_taskflow_api.html), there seems to be no way to block XCom return value logs.
   > 
   > ```python
   > @task
   > def my_task(): # Guess it is `_PythonDecoratedOperator`
   >     # ... process
   >     return large_data
   > 
   > 
   > with DAG(...) as dag:
   >     data = my_task() # It will make a huge log messages on Airflow UI
   >     my_second_task(data)
   > ```
   > 
   > so, I think additional work will be required in a separate PR for TaskFlow API users.
   
   https://github.com/apache/airflow/pull/19378#issuecomment-967047503
   > 
   > 
   > Yes we should do something for this but separately. Maybe something like (just a random idea)
   > 
   > ```python
   > @task(..., log_return_value="DEBUG")
   > def my_task():
   >     ...
   >     return large_data
   > ```
   
   
   
   ### Committer
   
   - [X] I acknowledge that I am a maintainer/committer of the Apache Airflow project.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org