This is an automated email from the ASF dual-hosted git repository.
weilee pushed a commit to branch v3-1-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v3-1-test by this push:
new 7649afdf415 [v3-1-test] Note asset event extra storage (#57727)
(#57734)
7649afdf415 is described below
commit 7649afdf4158b19e33c9f91d25ea49742f161238
Author: Wei Lee <[email protected]>
AuthorDate: Tue Nov 4 18:24:43 2025 +0800
[v3-1-test] Note asset event extra storage (#57727) (#57734)
Co-authored-by: Tzu-ping Chung <[email protected]>
---
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 22aea6faf34..7e06d0344a5 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
