Skip to content

Upgrade to Chroma Vector database API v2 #2685

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

Conversation

dev-jonghoonpark
Copy link
Contributor

@dev-jonghoonpark dev-jonghoonpark commented Apr 10, 2025

ChromaDB 1.0.0 has recently been released.

With this release, the v1 APIs have been completely deprecated.
To support the new v2 APIs, we need to upgrade API implementation.

related issues

@ilayaperumalg ilayaperumalg self-assigned this Apr 16, 2025
@ilayaperumalg ilayaperumalg added this to the 1.0.0-RC1 milestone Apr 16, 2025
@markpollack
Copy link
Member

Thank you very much!

@dev-jonghoonpark dev-jonghoonpark force-pushed the chroma-vector-database-v2 branch from f7840db to 452dba6 Compare April 16, 2025 13:20
@dev-jonghoonpark
Copy link
Contributor Author

dev-jonghoonpark commented Apr 16, 2025

@ilayaperumalg I have completed the rebase to resolve the conflict.

@dev-jonghoonpark
Copy link
Contributor Author

recently, testcontainers-java 1.21.0 is released
this version include support of new version chroma. (related pr: testcontainers/testcontainers-java#10170)

By upgrading the version of testcontainers-java, we can remove the temporal overridden wait strategy in this pr:

static {
    chromaContainer.waitingFor(new AbstractWaitStrategy() {
        @Override
        protected void waitUntilReady() {
            Wait.forHttp("/api/v2/heartbeat");
        }
    });
}

If you want, I can update the PR. But it’s fine to leave it as is.

@ilayaperumalg

@ElishebaW
Copy link

I'm having these issues as well. Any idea when this issue will be merged?

@ilayaperumalg
Copy link
Member

@dev-jonghoonpark Please go ahead and update the PR with your suggestion.
@ElishebaW We target to merge this soon and be available for RC1. Thanks for your patience on this.

@ElishebaW
Copy link

@ilayaperumalg Thank you so much!

@dev-jonghoonpark dev-jonghoonpark force-pushed the chroma-vector-database-v2 branch from 452dba6 to 2d3c26c Compare May 1, 2025 20:58
Signed-off-by: jonghoonpark <dev@jonghoonpark.com>
@dev-jonghoonpark dev-jonghoonpark force-pushed the chroma-vector-database-v2 branch from 2d3c26c to 201433e Compare May 1, 2025 21:00
@dev-jonghoonpark
Copy link
Contributor Author

dev-jonghoonpark commented May 1, 2025

  • upgraded test-container version for chroma and removed the temporal overridden wait strategy
  • removed @Disabled in ChromaVectorStoreAutoConfigurationIT.addAndSearchWithFilters (related pr: Migrate vector store auto-configurations to dedicated modules #2391)
    • The changes included in this PR seem to fix the issues that were previously present, and everything appears to be working correctly now.

@ilayaperumalg
Copy link
Member

@dev-jonghoonpark Thank you once again for the PR upgrading Chroma vector database to use v2 API. Rebased and merged as 09a6a6e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants