sunank200 opened a new pull request, #43678:
URL: https://github.com/apache/airflow/pull/43678
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
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/
-->
This PR removes the `execution_date` and `logical_date` arguments from
`api_connexion` that are used to retrieve DAG runs, aligning with the broader
changes introduced in Airflow 2.2 and preparing for Airflow 3.0. The functions
now use `run_id` as the sole identifier for DAG runs, simplifying the process
and eliminating deprecated behaviour.
### **Motivation**:
In Airflow, `execution_date` has historically been used to distinguish
different DAG run instances. However, the introduction of `run_id` and the DAG
run concept in Airflow 2.2 shifts away from using `execution_date` as an
identifier. Continuing to rely on `execution_date` introduces limitations, such
as the inability to handle multiple DAG runs at the same logical time,
especially in cases like `TriggerDagRunOperator` when dynamic runs are
generated.
By removing `execution_date` in favor of `run_id`, this PR eliminates these
limitations. This also removes the unique constraint on `execution_date` at the
database level, paving the way for a cleaner and more flexible scheduling
system in Airflow 3.0.
<!-- Please keep an empty line above the dashes. -->
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information.
In case of fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+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 a
newsfragment file, named `{pr_number}.significant.rst` or
`{issue_number}.significant.rst`, in
[newsfragments](https://github.com/apache/airflow/tree/main/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]
