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

MongoDB Vector Database File Upload requires "Id" despite MongoDB Atlas automatically assigning an ID. #4728

Open
mattbeardey opened this issue Dec 17, 2024 · 2 comments · Fixed by #4746
Labels
0.2 Issues which are related to the pre 0.4 codebase

Comments

@mattbeardey
Copy link

What happened?

In autogen.agentchat.contrib.vectordb.mongodb.py Line 295, the sanity check requires docs to have and "id", MongoDB Atlas can auto assign an ID, and therefore this is a roadblock for users looking to use the Auto ID feature. Uploading without ID is acceptable, but not possible.

What did you expect to happen?

Files should be able to be uploaded with just a {"content" : XXXXX} dictionary, without {"id":XX, "content":XXXXX}.

How can we reproduce it (as minimally and precisely as possible)?

Run a MongoDBAtlasVectorDB instance, and run the MongoDBAtlasVectorDB.insert_docs(docs = [{"content" : "This is dummy content"}], collection_name = "dummy_collection")

AutoGen version

0.2.40

Which package was this bug in

AgentChat

Model used

GPT3.5 (irrelevant)

Python version

3.12

Operating system

Windows (Code Spaces)

Any additional info you think would be helpful for fixing this bug

Example Auto ID, from simply uploading the Content + Vector.
Image

@ekzhu
Copy link
Collaborator

ekzhu commented Dec 17, 2024

Would you like to submit a fix?

@ekzhu ekzhu added the 0.2 Issues which are related to the pre 0.4 codebase label Dec 17, 2024
@mattbeardey
Copy link
Author

PR Raised at #4746 , Thanks

@ekzhu ekzhu linked a pull request Dec 18, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.2 Issues which are related to the pre 0.4 codebase
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants