GitHub user potiuk added a comment to the discussion: Where should DataInterval invariants be enforced in Airflow?
There were lots of discussions on that and I think the current conclusion and intention is expressed here (but you might want to follow earlier discussions): https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=337676722#Option2clarificationdocWIP-Resolutionofquestions Earlier discussions: * https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-83+Rename+execution_date+-%3E+logical_date+and+make+logical_date+optional * https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-83+amendment+to+support+classic+Airflow+authoring+style If you find any missing or unclear implementation or things to improve related to those conclusions, PRs to fix those are best way to discuss it. Ideally - if you see any improvement to current implementation - opening a PR with a proposal to improve it, and justification (ideally referring to those earlier discussions) is a good idea. Also if you feel that better capturing of the current state is needed, the best way to fix it is that someone like you - who is trying to figure it out, make a PR and propose it in the way they understand it - then when we see PR we will be able to point out any misunderstanding and things to correct before merge. This is by far most efficient and best way to create such a documentation - because people like you are best to formulate the explanations in the way that other people like you who have no earlier assumptions will find easiest to understand and learn from GitHub link: https://github.com/apache/airflow/discussions/59868#discussioncomment-15356363 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
