RNHTTR commented on code in PR #67392: URL: https://github.com/apache/airflow/pull/67392#discussion_r3395951761
########## airflow-core/docs/authoring-and-scheduling/assets.rst: ########## @@ -328,12 +328,18 @@ The shorthand for this is ``@asset.multi``: Dynamic data events emitting and asset creation through AssetAlias ----------------------------------------------------------------------- -An asset alias can be used to emit asset events of assets with association to the aliases. Downstreams can depend on resolved asset. This feature allows you to define complex dependencies for Dag executions based on asset updates. +Use ``AssetAlias`` when a task must declare an asset dependency before the concrete asset URI is +known. The alias is listed in ``outlets`` as a stable name, and the task resolves it at runtime by Review Comment: What does "stable name" mean? What does "concrete" mean? ########## airflow-core/docs/authoring-and-scheduling/assets.rst: ########## @@ -328,12 +328,18 @@ The shorthand for this is ``@asset.multi``: Dynamic data events emitting and asset creation through AssetAlias ----------------------------------------------------------------------- -An asset alias can be used to emit asset events of assets with association to the aliases. Downstreams can depend on resolved asset. This feature allows you to define complex dependencies for Dag executions based on asset updates. +Use ``AssetAlias`` when a task must declare an asset dependency before the concrete asset URI is +known. The alias is listed in ``outlets`` as a stable name, and the task resolves it at runtime by +adding one or more concrete ``Asset`` objects through ``outlet_events`` or yielded ``Metadata``. +Downstream Dags can depend on the alias, and Airflow triggers them when events are emitted for the Review Comment: "trigger" is kind of an overloaded term in Airflow. Maybe we should say "...and Airflow initiates a Dag run when..." -- 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]
