Skip to content
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

MongoDBChatMessageHistory saves History as a string rather than an object #20486

Open
5 tasks done
georgeherby opened this issue Apr 15, 2024 · 1 comment
Open
5 tasks done
Labels
design-question Ɑ: memory Related to memory module 🔌: mongo Primarily related to Mongo integrations

Comments

@georgeherby
Copy link

Checked other resources

  • I added a very descriptive title to this issue.
  • I searched the LangChain documentation with the integrated search.
  • I used the GitHub search to find a similar question and didn't find it.
  • I am sure that this is a bug in LangChain rather than my code.
  • The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code

                final_chain = ConversationalRetrievalChain.from_llm(
                    llm=llm,
                    retriever=retriever,
                    memory=memory,
                    verbose=True
                )

Error Message and Stack Trace (if applicable)

No response

Description

I am using MongoDBChatMessageHistory and it is working as expected in terms of functionality but I would expect the history record to be saved in an object in MongoDB rather than a string to aid with readability in the database.

(as an aside I am not sure why the fields are not snake or camelcase...)

image

System Info

langchain==0.1.13
langchain-community==0.0.29
langchain-core==0.1.36
langchain-mongodb==0.1.3
langchain-openai==0.1.1
langchain-text-splitters==0.0.1
langchainhub==0.1.15
@dosubot dosubot bot added Ɑ: memory Related to memory module 🔌: mongo Primarily related to Mongo integrations 🤖:bug Related to a bug, vulnerability, unexpected error with an existing feature labels Apr 15, 2024
@eyurtsev eyurtsev added design-question and removed 🤖:bug Related to a bug, vulnerability, unexpected error with an existing feature labels Apr 16, 2024
@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Jul 16, 2024
@dosubot dosubot bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 23, 2024
@dosubot dosubot bot removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Jul 23, 2024
@georgeherby
Copy link
Author

This is still a problem..

@dosubot dosubot bot reopened this Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design-question Ɑ: memory Related to memory module 🔌: mongo Primarily related to Mongo integrations
Projects
None yet
Development

No branches or pull requests

2 participants