Immutable solution version
ChromaDB 0.4+ is no longer compatible with client config
Complete solution
Covers this LangChain problem: ChromaDB 0.4+ is no longer compatible with client config. [mrinterestfull (reporter)]: The deprecated configuration of Chroma error came from old langchain, not chroma.
The problem
Issue langchain-ai/langchain#7887 (closed, 51 comments): ### System Info
- Python 3.9.13
- langchain-0.0.235-py3-none-any.whl
- chromadb-0.4.0-py3-none-any.whl
Who can help?
No response
Information
- [ ] The official example notebooks/scripts
- [x] My own modified scripts
Related Components
- [ ] LLMs/Chat Models
- [ ] Embedding Models
- [ ] Prompts / Prompt Templates / Prompt Selectors
- [ ] Output Parsers
- [ ] Document Loaders
- [X] Vector Stores / Retrievers
- [ ] Memory
- [ ] Agents / Agent Executors
- [ ] Tools / Toolkits
- [ ] Chains
- [ ] Callbacks/Tracing
- [ ] Async
Reproduction
Steps to reproduce:
1....
What fixed it
[mrinterestfull (reporter)]: The deprecated configuration of Chroma error came from old langchain, not chroma. Upgrading langchain from 0.0.228 to 0.0.325 fixed it. Another reporter's case was caused by a stale chromadbimpl='duckdb+parquet' in their .env; removing it fixed that.
Evidence
In gh:langchain-ai/langchain#7887 (LangChain), the issue reported was: Issue langchain-ai/langchain#7887 (closed, 51 comments): ### System Info
- Python 3.9.13
- langchain-0.0.235-py3-none-any.whl
- chromadb-0.4.0-py3-none-any.whl
Who can help?
No response
Information
- [ ] The official example notebooks/scripts
- [x] My own modified scripts
Related Components
- [ ] LLMs/Chat Models
- [ ] Embedding Models
- [ ] Prompts / Prompt Templates / Prompt Selectors
- [ ] Output Parsers
- [ ] Document Loaders
- [X] Vector Stores / Retrievers
- [ ] Memory
- [ ] Agents / Agent Executors
- [ ] Tools / Toolkits
- [ ] Chains
- [ ] Callbacks/Tracing
- [ ] Async
Reproduction
Steps to reproduce:
1.... The verified resolution from the thread: [mrinterestfull (reporter)]: The deprecated configuration of Chroma error came from old langchain, not chroma. Upgrading langchain from 0.0.228 to 0.0.325 fixed it. Another reporter's case was caused by a stale chromadbimpl='duckdb+parquet' in their .env; removing it fixed that. Source: mount the host path https at container path //github.com/langchain-ai/langchain/issues/7887
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_yk_jTPc_5mjpaKMIixfiFQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">ChromaDB 0.4+ is no longer compatible with client config <span>— Vectle</span></a>