Re: [I] Provide consumer DAGs with context about the dag run(s) of its producer(s) [airflow]

["uranusjr (via GitHub)" <gi...@apache.org>]

uranusjr commented on issue #33088:
URL: https://github.com/apache/airflow/issues/33088#issuecomment-3489670394

   You can access the asset events that triggered to the downstream dag run with `triggering_asset_events`, and for each event, there are fields `source_task_id` `source_dag_id` etc. that provide information on the producing task instance object.
   
   For the schedule part:
   
   * You can use `source_dag_id` to get dag information through API if that’s what you want (this will be a text representation)
   * If what you really want to do is to derive a _time period_ based on the upstream schedule, we are currently in the process to propose a structured way to do this with [asset partitions](https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-76%2BAsset%2BPartitions).
   * [You can always manually attach whatever information you want to the asset event when it is emitted.](https://airflow.apache.org/docs/apache-airflow/stable/authoring-and-scheduling/assets.html#attaching-extra-information-to-an-emitting-asset-event) Each event in the downstream should also have the `extra` attribute containing those manually set data.
   
   I think this covers all use cases.


-- 
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-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org