langchain-ai/langchain

ChromaDB document deletion not working

Closed

#4,880 opened on May 17, 2023

View on GitHubContributor guide
 (25 comments) (3 reactions) (0 assignees)Python (22,617 forks)batch import
chromaexternalhelp wantedintegration

Repository metrics

Stars
 (136,758 stars)
PR merge metrics
 (Avg merge 10d 2h) (288 merged PRs in 30d)

Description

Issue you'd like to raise.

I am trying to delete a single document from Chroma db using the following code:

chroma_db = Chroma(persist_directory = embeddings_save_path, embedding_function = OpenAIEmbeddings(model = os.getenv("EMBEDDING_MODEL_NAME"), chunk_size = 1, max_retries = 5) )

chroma_db._collection.delete(ids = list_of_ids) chroma_db.persist()

However, the document is not actually being deleted. After loading/re-loading the chroma db from local, it is still showing the document in it.

I have tried the following things to fix the issue:

I have made sure that the list of ids is correct. I have tried deleting the document multiple times. I have tried restarting the Chroma db server. None of these things have worked.

I am not sure why the document is not being deleted. I would appreciate any help in resolving this issue.

Thanks, Anant Patankar

Suggestion:

No response

Contributor guide

Research direction
Investigate the Chroma class in langchain's vectorstores implementation, specifically the ` collection.delete` and `persist` methods. Check if the deletion is actually persisted to disk or if there is a caching issue. Look at the ChromaDB documentation for the correct delete workflow. Examine the GitHub issue comments for any attempted solutions or reproduction steps.
Tech stack
python
Domain
databasebackend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Python basicsLangChain basicsChromaDB basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40