Skip to content

fix(pgvector-java): document released Central setup - #1065

Open
nik13 wants to merge 2 commits into
mainfrom
fix/pgvector-java-central-setup
Open

nik13 wants to merge 2 commits into
mainfrom
fix/pgvector-java-central-setup

Conversation

@nik13

@nik13 nik13 commented Oct 31, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Replace stale pgvector JitPack/main-SNAPSHOT coordinates with the released Maven Central com.futureagi:traceai-java-pgvector:1.0.0, pgvector-java 0.1.6, and PostgreSQL JDBC 42.7.14 dependencies.
  • Make the example work on that published release by registering upstream pgvector types on the same explicitly borrowed connection used for searches. No copied instrumentation helper, unreleased package, or new public API is required.
  • Explain the fixed id/embedding/metadata schema, connection ownership, and the difference from standard OpenTelemetry JDBC instrumentation. Preserve the raw-SQL filter warning and use a small complete vector example.
  • Add a documentation regression test. Only the pgvector section changes; the concurrent Qdrant, MongoDB, and ChromaDB PRs address different sections of the shared page.

Validation

  • Extracted the page's literal Maven dependencies and Java example into a fresh standalone consumer. Dependencies resolved from Maven Central into an empty local repository, independently of locally installed traceAI artifacts.
  • The published 1.0.0 example compiled and executed against disposable PostgreSQL 16/pgvector 0.8.1, inserted a real vector, created an HNSW index, and completed both nonempty searches. Output: doc-1.
  • The execution used synthetic local database data, a clean environment without Future AGI credentials, and sandbox-exec denying outbound network except localhost. No Cloud/vendor calls were made.
  • npm run test:integrations: 10 passed.
  • npm run build: passed, 794 pages indexed.
  • npm run audit-links: zero broken navigation/content links; 28 existing orphan pages.
  • Inspected the built page in isolated desktop Chrome: HTTP 200, no page errors, dependency block and per-connection warning rendered correctly.

This docs PR can ship with today's registry packages. The general DataSource decoding and error-status fix is separately proposed in future-agi/traceAI#433; this page does not depend on that release.

E2E coverage

not applicable (no product e2e/ harness) · flows hit: n/a · marker: n/a · verdict: not applicable

🤖 Generated with Claude Code

nik13 and others added 2 commits October 31, 2026 10:17
…gistration

Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>

This branch has not been deployed

No deployments
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.

2 participants