From ff431d119374cde0d7cc1ab79ae584d980c5c820 Mon Sep 17 00:00:00 2001 From: Tzu-ping Chung Date: Mon, 3 Nov 2025 15:15:54 +0800 Subject: [PATCH] Note asset event extra storage --- airflow-core/docs/authoring-and-scheduling/assets.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/airflow-core/docs/authoring-and-scheduling/assets.rst b/airflow-core/docs/authoring-and-scheduling/assets.rst index 22aea6faf34fa..7e06d0344a52f 100644 --- a/airflow-core/docs/authoring-and-scheduling/assets.rst +++ b/airflow-core/docs/authoring-and-scheduling/assets.rst @@ -178,6 +178,8 @@ Another way to achieve the same is by accessing ``outlet_events`` in a task's ex There's minimal magic here---Airflow simply writes the yielded values to the exact same accessor. This also works in classic operators, including ``execute``, ``pre_execute``, and ``post_execute``. +.. note:: Asset event extra information can only contain JSON-serializable values (list and dict nesting is possible). This is due to the value being stored in the database. + .. _fetching_information_from_previously_emitted_asset_events: Fetching information from previously emitted asset events