jroachgolf84 commented on PR #67248: URL: https://github.com/apache/airflow/pull/67248#issuecomment-4539111717
> I just looked at #67376 and I meant exactly this same mechanism but for asset. Cannot we plumb through automatically the state of an asset to its related triggers? That would avoid forcing Dag author to manually get the asset state with `AssetState(name=self.asset_name)` @vincbeck - I think that makes sense. The only caveat is that a `BaseEventTrigger` can have multiple Assets "plumbed" through to it (as we discussed here: https://github.com/apache/airflow/pull/66595). That would make the pattern for access the state for a specific Asset a bit more difficult. I guess the syntax would be something more like this: ```python # Contains the asset states self.asset_states = ... asset_a_state = self.asset_states.get("asset_a") asset_b_state = self.asset_states.get("asset_b") ``` Thoughts? I'm kinda caught in the middle on this one. -- 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]
