-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Add serialization/deserialization support to State
#9286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @sjrl , I’ve put together a small “playground” demo that reproduces the missing serialization on
Let me know if this captures the right direction—I’ll package it up into a formal PR once we agree on the approach. |
Not sure if this is related, but it seems like |
|
When
State
was originally added (code here) we did not add serialization/deserialization support for it since it was not immediately needed.However, for Pipeline Checkpoints and better traces (see deepset-ai/haystack-core-integrations#1664) we should add support for serialization and deserialization.
I believe basing the
to_dict
off of something like ourcoerce_tag_value
could work or taking inspiration from the Pipeline breakpoints PR deepset-ai/haystack-experimental#271 and how they handled serialization/deserialization of inputs and outputs of components could help as well.The text was updated successfully, but these errors were encountered: