ChromaDB 0.4+ is no longer compatible with client config

[gpapp]

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. Create a Chroma store which is locally persisted

   store = Chroma.from_texts(
   texts=docs, embedding=embeddings, metadatas=metadatas, persist_directory=environ["DB_DIR"]
   )

2. Get the error You are using a deprecated configuration of Chroma. Please pip install chroma-migrate and runchroma-migrateto upgrade your configuration. See https://docs.trychroma.com/migration for more information or join our discord at https://discord.gg/8g5FESbj for help!
3. Suffer

Expected behavior

1. Create locally persisted Chroma store
2. Use Chroma store

The issue:

Starting chromadb 0.40 the chroma_db_impl is no longer a supported parameter, it uses sqlite instead.

Removing the line chroma_db_impl="duckdb+parquet", from langchain.vectorstores/chroma.py solves the issue, but the earlier DB cannot be used or migrated.

[dosubot[bot]]

Hi, @gpapp,

I'm helping the LangChain team manage their backlog and am marking this issue as stale. It seems like there has been a lot of discussion and troubleshooting around the compatibility issue with ChromaDB. Users have reported encountering errors related to deprecated configurations and attribute issues when using the latest versions of ChromaDB and LangChain. Some users have found success by downgrading to an older version of ChromaDB, while others have shared their settings and code snippets that have worked for them. The LangChain team has also provided guidance and suggestions for resolving the issue, including checking the versions of the libraries being used and ensuring proper configuration settings. The issue appears to be ongoing, with users continuing to seek assistance and share their experiences with different approaches.

Could you please confirm if this issue is still relevant to the latest version of the LangChain repository? If it is, please let the LangChain team know by commenting on the issue. Otherwise, feel free to close the issue yourself, or it will be automatically closed in 7 days. Thank you!