ashb opened a new pull request #18503:
URL: https://github.com/apache/airflow/pull/18503


   We know that this TI belongs to this relationship, so setting this
   avoids a lookup in a few places.
   
   This somehow feels like we are fighting SQLAlchemy a bit, but from what
   I can work out the only way to do this would either be an eager load of
   one form or another (which would make a more complex query or an extra
   query) or to look at `self.task_instances` -- which means the filtering
   would be done in python space -- which we want to avoid for large dags
   (it's not totally unheard of to have dags with 10 or 20k tasks in them!)
   
   
   Relates to #18359 (but is in addition to that PR)
   
   <!--
   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 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/
   -->
   
   ---
   **^ 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