Creating an Azure Table Checkpointer #1673
Unanswered
tyler-ball
asked this question in
Q&A
Replies: 1 comment
-
My first guess at this point is there is an issue in the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey Everyone, I am working on implementing a checkpointer for an Azure storage account, specifically using their Tables API. Here is my current implementation:
When I set this up using
memory = AzureTableSaver(connection_string=connection_string, table_name=table_name)
my little test application (simple ReAct graph fronted by streamlit) everything starts correctly. It even saves data to my tables correctly (as far as I can tell):If RowKey is a single UUID, then checkpoint and metadata are populated. If rowkey is of the form
1ef6f81b-5a1b-6c64-bfff-7e4ea0712529_235cd0db-4960-545e-9840-b1ea2e70a2fc_0
then checkpoint and metadata are not populated butchannel
andvalue
are populated. So I think that corresponds to those rows being writes entries.When I do a simple "Hi im bob" / "What is my name flow" the agent has no concept of the name bob, which does work when using the Memory Saver.
Any guess on where to start troubleshooting? I've been following the MongoDB / Redis examples, as well as referencing https://www.kaggle.com/code/pilarpieiro/example-cosmosdb-checkpointer-for-langgraph
Beta Was this translation helpful? Give feedback.
All reactions