Using v1.0.3 client/server with a database created by v0.6.3 client/server causes `chromadb.errors.InternalError`

What this teaches

How to using v1.0.3 client/server with a database created by v0.6.3 client/server causes chromadb.errors.InternalError.

The problem

Issue chroma-core/chroma#4217 (closed, 27 comments): ### What happened? A collection.get() call using v1.0.3 client and v1.0.3 server on a collection created by v0.6.3 chromadb produced a chromadb.errors.InternalError: Error executing plan: Error sending backfill request to compactor. This is the relevant code snippet: ``python await collection.get( where={"path": full_path_str}, include=["metadatas"], ) `` Aside from this error, I'm wondering whether a database created by 0.x.

What worked (verified answer)

Using a v1.0.x client/server against a database created by v0.6.3 fails with chromadb.errors.InternalError because the 0.6.3-to-1.0.x migration (00005-max-seq-id-int.sqlite.sql) failed to apply cleanly. Maintainer-verified fix: delete the failed migration record, then re-run your query: sqlite3 [persist_dir]/chroma.sqlite3 "delete from migrations where dir='metadb' and filename='00005-max-seq-id-int.sqlite.sql';". Also, if you have a large base of existing 0.6.3 users, pin the 0.6.3 version for now rather than upgrading across the 1.0 boundary until the upgrade path is hardened.

Source

gh:chroma-core/chroma#4217 - https://github.com/chroma-core/chroma/issues/4217

In gh:chroma-core/chroma#4217, the reporter ran into: Issue chroma-core/chroma#4217 (closed, 27 comments): ### What happened? A collection.get() call using v1.0.3 client and v1.0.3 server on a collection created by v0.6.3 chromadb produced a chromadb.errors.InternalError: Error executing plan: Error sending backfill request to compactor. This is the relevant code snippet: ``python await collection.get( where={"path": full_path_str}, include=["metadatas"], ) `` Aside from this error, I'm wondering whether a database created by 0.x. The verified answer was: Using a v1.0.x client/server against a database created by v0.6.3 fails with chromadb.errors.InternalError because the 0.6.3-to-1.0.x migration (00005-max-seq-id-int.sqlite.sql) failed to apply cleanly. Maintainer-verified fix: delete the failed migration record, then re-run your query: sqlite3 [persist_dir]/chroma.sqlite3 "delete from migrations where dir='metadb' and filename='00005-max-seq-id-int.sqlite.sql';". Also, if you have a large base of existing 0.6.3 users, pin the 0.6.3 version for now rather than upgrading across the 1.0 boundary until the upgrade path is hardened. Source issue: https://github.com/chroma-core/chroma/issues/4217