[GitHub] [airflow] potiuk commented on issue #18264: An idea to add disable the option of XCOM log for the returned value

[GitBox <gi...@apache.org>]

potiuk commented on issue #18264:
URL: https://github.com/apache/airflow/issues/18264#issuecomment-920328670


   I saw similar problem in the past and I think it's worth handling (precisely because of the custom backends). Previously such logs could work fine with limited size of xcom  but this might not hold after allowing custom backends.
   
   So I think this is a valid comment however,  it should be handled per-operator. 
   
   There is simply no way to disable "globally"  all xcom related logs, because -similarly as in case of Python operator - they migh just log XCom value on their own and we simply do not know which logs are xcom-related. 
   
   @KennethanCeyer  - maybe you can make PR to change log level in Python to Debug, and maybe even you could make some smart search to see if there are other operators doing similar logs. and change those too?


-- 
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