This is an automated email from the ASF dual-hosted git repository.
Lee-W pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 602e74a22a6 Clarify AssetAlias usage (#67392)
602e74a22a6 is described below
commit 602e74a22a60489fd7bcc81388ddf77cd5aa50de
Author: Silva Dev BR <[email protected]>
AuthorDate: Wed Jul 29 07:50:44 2026 -0300
Clarify AssetAlias usage (#67392)
Co-authored-by: Wei Lee <[email protected]>
---
airflow-core/docs/authoring-and-scheduling/assets.rst | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/airflow-core/docs/authoring-and-scheduling/assets.rst
b/airflow-core/docs/authoring-and-scheduling/assets.rst
index 3bd84a054d0..bc62e79318c 100644
--- a/airflow-core/docs/authoring-and-scheduling/assets.rst
+++ b/airflow-core/docs/authoring-and-scheduling/assets.rst
@@ -360,12 +360,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
Asset's fixed attributes
+(like URI or name) are available. 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 resolved assets.
How to use AssetAlias
~~~~~~~~~~~~~~~~~~~~~~~
-``AssetAlias`` has one single argument ``name`` that uniquely identifies the
asset. The task must first declare the alias as an outlet, and use
``outlet_events`` or yield ``Metadata`` to add events to it.
+``AssetAlias`` has one single argument ``name`` that uniquely identifies the
alias. The task must
+first declare the alias as an outlet, and then use ``outlet_events`` or yield
``Metadata`` during
+execution to associate the alias with the concrete assets it produced.
The following example creates an asset event against the S3 URI
``f"s3://bucket/my-task"`` with optional extra information ``extra``. If the
asset does not exist, Airflow will dynamically create it and log a warning
message.
