Support for set in XCom serialization
See original GitHub issueDescription
Add support for set
in Xcom serialization method. This requires support for set
in nested structures.
Use case / motivation Once we switched to JSON as main serialization format the following error appeared:
TypeError: Object of type 'set' is not JSON serializable
Related Issues
Discussion started in https://github.com/apache/airflow/pull/8607#discussion_r419327697
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (14 by maintainers)
Top Results From Across the Web
XComs — Airflow Documentation
An XCom is identified by a key (essentially its name), as well as the task_id and dag_id it came from. They can have...
Read more >Airflow XCOM : The Ultimate Guide - Marc Lamberti
The Airflow XCom is not an easy concept, so let me illustrate why it might be ... Keep in mind that your value...
Read more >How to solve this Problem Could not serialize the XCom value ...
so xcom doesn't support exchanging non serialized data type like dataframes (read more about Python pickle here), but if you must , you...
Read more >Custom XCom backends | Astronomer Documentation
The final step to setting up your custom XCom backend is configuring your serialization and deserialization methods and applying them to your Airflow ......
Read more >Customizing Xcom to enhance data sharing between tasks
Presented by Vikram Koka & Ephraim Anierobi at Airflow Summit 2021.In Apache Airflow, Xcom is the default mechanism for passing data between ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
https://github.com/apache/airflow/pull/16786 should fix this
Let’s use Custom XCom backend if needed – this isn’t critical