Lee-W commented on issue #39017: URL: https://github.com/apache/airflow/issues/39017#issuecomment-2853148553
> However, I've run some experiments, and found that these information are not propagated to either the inlet_events or the triggering_asset_events Do you mean `extra`? I think they're there. Just not included in the `__repr__`. Also, you'll need to actally access the inlets. e.g., ```python inlet_events[Asset(name="abc")] ``` > I am wondering if it is the right approach to the issue? sounds reasonable to me > Is there any caveat I should keep in mind when populating the information in inlet_events and triggering_asset_events? `inlet_events` should be fine. But `inlet_events` is not something used to triggered a dag. It's more like an extra infomration a dag can requested from the history. `triggering_asset_events` should probably be fine as well 🤔 > I am looking at the InletEventsAccessors under task-sdk/src/airflow/sdk/execution_time/context.py. Is it the right place to look at and modify the information being included in inlet_events? kind of? depends on what kind of information. this is how we request the asset event history for a specific asset. e.g., the following logic is implemented here ```python inlet_events[Asset(name="abc")] ``` > Below is what I think about why this approach can resolve the issue. sounds reasonable to me -- 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
