Skip to content

fix(chromadb-java): document the released legacy setup - #1046

Merged
nik13 merged 3 commits into
mainfrom
fix/chromadb-java-released-legacy-setup
Nov 4, 2026
Merged

nik13 merged 3 commits into
mainfrom
fix/chromadb-java-released-legacy-setup

Conversation

@nik13

@nik13 nik13 commented Oct 31, 2026

Copy link
Copy Markdown
Contributor

Summary

Correct only the ChromaDB section of the Java vector-database guide.

  • Replace mutable JitPack coordinates with the published Maven Central core/instrumentation packages at 1.0.0 and explicitly install the provided Chroma Java client 0.1.7. Tell readers not to mix duplicate JitPack/core artifacts.
  • Place an actionable API-v1 compatibility warning before installation: Chroma 1.5.9 rejects v1 GETs with HTTP 410; this wrapper does not support v2-only servers. Never recommend downgrading or recreating a database.
  • Replace the incomplete snippet with a compilable query method using the application's existing collection/embedding function, complete imports and a link to initialization/privacy settings.
  • Add three regression tests and run them through the existing integration-test CI command.

Released-package verification

The example uses only published com.futureagi:traceai-java-core:1.0.0, com.futureagi:traceai-java-chromadb:1.0.0 and io.github.amikos-tech:chromadb-java-client:0.1.7. It does not depend on the concurrent package fix or advertise unreleased update tracing.

  • Extracted the Java code block unchanged into a standalone Maven consumer using an empty local Maven repository populated only from Central; compiled and ran it against synthetic localhost Chroma endpoints and a localhost OTLP receiver.
  • Asserted the real published client's v1 query route, returned document IDs, a decoded ChromaDB Query OTLP span, hidden input text with hideInputs(true), and the HTTP 410 lookup failure when v1 is unavailable.
  • All execution ran with outbound networking denied except localhost and without real credentials or vendor/model calls. This is not a claim of live Chroma server or dashboard verification.

Sources:

Tests and review

  • New page contract tests: 3 failed before the correction, 3 pass after.
  • 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.
  • Built page rendered in headless Chrome at desktop width: warning and dependency tabs inspected, no page errors. No fabricated product screenshot was added.
  • Internal-standards self-review completed; no application 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

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>
nik13 and others added 2 commits November 2, 2026 05:54
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>
@nik13
nik13 merged commit c4a111a into main Nov 4, 2026
8 checks passed
@nik13
nik13 deleted the fix/chromadb-java-released-legacy-setup branch November 4, 2026 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant