Repository navigation
fix(chromadb-java): document the released legacy setup - #1046
Merged
Merged
Conversation
Use Central coordinates, declare the provided client, and bound Java Chroma support to existing API-v1 deployments. Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
Resolve the integration test script conflict by retaining all main-branch suites and the ChromaDB Java regression suite. Co-Authored-By: Claude Code <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Correct only the ChromaDB section of the Java vector-database guide.
Released-package verification
The example uses only published
com.futureagi:traceai-java-core:1.0.0,com.futureagi:traceai-java-chromadb:1.0.0andio.github.amikos-tech:chromadb-java-client:0.1.7. It does not depend on the concurrent package fix or advertise unreleased update tracing.ChromaDB QueryOTLP span, hidden input text withhideInputs(true), and the HTTP 410 lookup failure when v1 is unavailable.Sources:
Tests and review
npm run test:integrations: 12 pass.npm run build: Astro + Pagefind succeed (existing redirect-page/orphan warnings remain).npm run audit-links: zero broken navigation links and zero broken content links.e2e/harness applies, and no UI implementation, migration or public application contract changed.No other database sections or the shared Java setup page are changed. Modern-server support remains held until a compatible released Java client and operation tests exist.
🤖 Generated with Claude Code