KennethanCeyer opened a new pull request #19378:
URL: https://github.com/apache/airflow/pull/19378


   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of an existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   related: #18264
   
   ---
   
   The current Airflow version (2.x.x) supports [Custom XCom 
Backends](https://www.astronomer.io/guides/custom-xcom-backends). and It means 
that the data from XCom could be larger than we think. (e.g. over `100GB`)
   
   However, `PythonOperator` and `LevelDBOperator` will try to show all of 
those data from XCom as a log message. It will break the web page (due to 
browser memory issue or rendering speed issue). and It will make it difficult 
to see the other log message from the task.
   
   This PR suggests changing the logLevel `info` to `debug`, Because XCom 
returned value can be treated `debug-purpose`
   
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to