uranusjr commented on issue #41014: URL: https://github.com/apache/airflow/issues/41014#issuecomment-2259633808
The behaviour is expected and (unfortunately) intended. When a run is scheduled, it is identified by its data interval, but a manually triggered run does not have a pre-defined interval to start with, so it is instead identified by the time it’s triggered (or the custom date you provide), and the data interval calculated from it. Notably, the data interval is calculated backwards because a run cannot start before the interval it covers ends, and calculating forward would force a trigger to wait for potentially a long time before it can actually kick start anything, which is not people want. This has been the behaviour since pre-historic times (in the sense that nobody really remembers who created it and why), and we couldn’t change it due to compatibility issues. But you’ve come at the right time! Airflow 3 is set to start development next month, and it will be possible to break compatibility in a major version bump. I think there’s already an issue somewhere for this, or I’m going to create one if I can’t find it. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
