rafaelwilliem opened a new pull request, #77206:
URL: https://github.com/apache/airflow/pull/77206

   Migrate the Execution API `GET /execution/dags/{dag_id}` (`get_dag`) 
endpoint from synchronous `SessionDep` to `AsyncSessionDep` so database reads 
yield the event loop without occupying a threadpool worker.
   
   Instead of calling `session.get(DagModel, dag_id)` (which selects all 35 
`DagModel` columns and lazily queries `dag_model.tags`), project only the 7 
`DagModel` columns required by `DagResponse` and `DagTag.name`, avoiding full 
`DagModel` and `DagTag` ORM entity hydration and lazy-loading on the async 
session.
   
   related: #67799
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Google Antigravity (Argon & Hydrogen)
   
   Generated-by: Google Antigravity following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).


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