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

[Bug]: "Collection is not created" message after upgrading to 0.5.0 #2837

Open
JINO-ROHIT opened this issue Sep 23, 2024 · 1 comment
Open
Labels
bug Something isn't working version-mismatch

Comments

@JINO-ROHIT
Copy link

What happened?

My current chroma vector db was indexed in version 0.4 and using that it gave me an error "sqlite3.OperationalError: no such column: collections.topic"

So I upgraded version to 0.5 and now I get this error message and my vector db is not being queried and always returns empty .

Versions

Chroma 0.5

Relevant log output

No response

@JINO-ROHIT JINO-ROHIT added the bug Something isn't working label Sep 23, 2024
@tazarov
Copy link
Contributor

tazarov commented Sep 24, 2024

@JINO-ROHIT, this is generally an issue with version mismatch. When you upgrade to newer chroma e.g. 0.4.24->0.5.7 there are some system DB upgrades that are carried out (not always but sometimes). These upgrades generally are not backward compatible, and you generally won't be able to access your DB with a client version inferior to the one you used for the upgrade.

Regarding the specific error, that is a sqlite3 error when the client tries to access a column that has been removed/deprecated (I think this change was done somewhere in the late 0.4.2x). It happens if you try to access your upgraded DB with earlier version. Can you double check that you are accessing your DB with 0.5.x client?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working version-mismatch
Projects
None yet
Development

No branches or pull requests

3 participants