Fix DagRun data interval for DeltaDataIntervalTimetable #35391
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bolkedebruin
approved these changes
Nov 6, 2023
romsharon98
pushed a commit
to romsharon98/airflow
that referenced
this pull request
Nov 10, 2023
VladaZakharova
pushed a commit
to lwyszomi/airflow
that referenced
this pull request
Nov 13, 2023
…ome location Fix DagRun data interval for DeltaDataIntervalTimetable (apache#35391)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When providing a timedelta as a schedule and setting catchup to False, the dag run data interval is not rounded to the correct start/end data interval dates. The tests were passed by adding
tick=Falseto@time_machine.travelwhich hid the bug.