uranusjr commented on issue #55489: URL: https://github.com/apache/airflow/issues/55489#issuecomment-3490091049
As mentioned above, you can just pass the information in the event extra if you want. We explcitly removed data interval (and logical date) from the downstream dag run in Airflow 3 since it is impossible to create a logic that generates a data interval for asset-triggered dags that’s meaningful for everyone, especially since a dag can depend on more than one asset, potentially declared on dags with different schedules. We are working on a new, more generic concept called asset partitions that would allow you to declare how you want to derive intervals from upstream schedules. This will also be available in time-scheduled dag runs (and eventually replace data intervals), so time and asset-triggered dag scheduling can use the same interface to retrieve information. -- 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]
