Repository navigation
docs(elasticsearch): use native Java tracing across client majors - #1084
Merged
Merged
Conversation
Replace the incomplete snapshot-wrapper setup with published native OpenTelemetry dependencies. Exercise exact sync, async and KNN snippets on 8.12.0 and 9.5.5 through loopback OTLP and the production converter; retain the released wrapper only for its supported retrieval enrichment. Co-Authored-By: Claude Code <noreply@anthropic.com>
sudo changes Java user.home independently of HOME; use the same Maven repository for dependency resolution and network-isolated execution. Co-Authored-By: Claude Code <noreply@anthropic.com>
Resolve RUNNER_TEMP at step execution and pass the path through GITHUB_ENV; runner context is unavailable in job-level env. Validated with actionlint. Co-Authored-By: Claude Code <noreply@anthropic.com>
The client future can complete before native instrumentation finishes exporting its span. Bound the wait for the first export rather than assuming response completion makes it immediately visible; keep exact span-count and parentage assertions. 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
com.futureagi:traceai-java-elasticsearch:1.0.1wrapper as optional retrieval enrichment on its supported 8.12.0 client. Its KNN builder lambda throwsClassCastExceptionon 9.5.5; the guide explicitly directs 9.x users to native tracing instead. No wrapper API is removed or changed.Verification
main.future-agi/future-agi@215b19543a47de8c7ae7e8dc452dc267440e5c8d. Native spans retain database attributes as generic (unknown) observations, not invented semantic retrievers. The optional retrieval parent preserves its semantic kind and parentage.actionlint.Scope
Documentation and regression coverage only; no SDK release or product change. No real Elasticsearch cluster, Future AGI Cloud credentials, or customer data was used. The production converter check does not claim live authentication, storage, or UI ingestion. No new product screenshot was fabricated.
🤖 Generated with Claude Code