Open pseudotensor opened 6 months ago
I've also encountered this issue today when running a a script that worked the week before last.
I did some looking around at commits and I think I found the problem. The third party tool you are using is likely using an older version of chroma (something like 0.4.x) because the topic column was removed in the latest version of chroma 0.5.0 (see https://github.com/chroma-core/chroma/pull/1933)
So if you have a version mismatch (say a new instance of chromadb and an older script/tool using it) you will get this error
@pseudotensor, in 0.4.24
, we phased out a column in the SQLite DB. The change is not backward compatible for clients. That means that if you have a DB created or accessed with 0.4.24
, we apply a migration to the chroma.sqlite3
file, which is non-reversible, and any older client will give you the above exception.
I think this is due to a version mismatch with 0.5. Can you confirm if that solves your issue ?
switching to 0.5 solves the issue
UPDATE: now I am facing this error when using collection.query
chromadb Exception: {"error":"AttributeError(\"type object 'QueryEmbedding' has no attribute 'model_validate'\")"}
@aliyassine26, this is due to an older version of pydantic
. Can you bump your pydantic
version to 2.x+
I have a Chroma version: 0.4.22 , SQLite version: 3.42.0 , Python 3.11.9 still getting the issue
Exception has occurred: OperationalError
no such column: collections.topic
File "C:\Users\SayantaniGhosh\Documents\IBM24\GenAI_WatsonX_Usecase_DIAGEO\git_repo\test_bpmn_fiori\services\test1.py", line 34, in fetch_all_docs
db3 = Chroma(persist_directory="./db_manager/chroma_db_impact", embedding_function=embeddings1)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\SayantaniGhosh\Documents\IBM24\GenAI_WatsonX_Usecase_DIAGEO\git_repo\test_bpmn_fiori\services\test1.py", line 54, in
@Sayantanighosh17github, this issue appears when you have accessed your Chroma persistent data with 0.5.0
version. Chroma does a schema migration from 0.4.x->0.5.x. To resolve start using Chroma 0.5.0
.
Thanks you guys so much!
What happened?
Versions
chroma 0.4.23 python 3.10.
A user of h2oGPT hit this, unsure why. Any ideas?
Relevant log output
No response