[
https://issues.apache.org/jira/browse/SOLR-15797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443985#comment-17443985
]
Chris M. Hostetter commented on SOLR-15797:
-------------------------------------------
I suspect this will likely mean either:
* Adding {{io.opentracing}} as a SolrJ dependency to pull in the Span info
from the GlobalTracer (or a Tracer impl specified in the SolrClient Builder)
** A plus side of this approach would mean that some of the existing code in
solr/core around decorating http update & query requests could "go ahead" and
just let the SOlrJ code do it's thing
* Adding some new general plugin hook to our SolrClient impls to "decorate"
HTTP requests so that a new contrib/plugin can be written that depends on
{{io.opentracing}} to decorate the HTTP requests with the necessary headers
> SolrJ Tracer support
> --------------------
>
> Key: SOLR-15797
> URL: https://issues.apache.org/jira/browse/SOLR-15797
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Chris M. Hostetter
> Priority: Major
>
> It's not currently possible (or at least: not very easy out of the box) for a
> SolrJ client application to specify distributed Tracing information in a
> request to Solr such that Solr's Tracer support will recognize that the
> request is part of a a larger Span.
> We should figure out & documented a recommended way of doing this
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
