ej-sanmartin opened a new pull request, #60861:
URL: https://github.com/apache/airflow/pull/60861

   * closed: #51758 
   
   Adds support for ordering DAG runs by deadline in the list DAG runs API 
endpoints.
   
   Accomplished by:
   
   - Added deadline as a valid order_by option for both:
     - GET /dags/{dag_id}/dagRuns (list DAG runs)
     - POST /dags/dagRuns/list (batch list DAG runs)
   - Introduced a correlated subquery (_earliest_deadline_subquery) that 
selects the minimum (earliest) deadline time for each DAG run, enabling proper 
sorting by deadline
   
   Includes updated test for cover this behavior.
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [ ] Yes (please specify the tool below)
   
   <!--
   Generated-by: [Tool Name] 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` or `{issue_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