[
https://issues.apache.org/jira/browse/HBASE-23811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17244636#comment-17244636
]
Duo Zhang commented on HBASE-23811:
-----------------------------------
I wonder whether we should do this.
The tracing system needs a backend to collect the tracing data, which is not
part of HBase, so if we tie HBase together with Jaeger, what if the users want
to use Apache SkyWalking?
So I expect that, we just ship with the OpenTracing or OpenTelemetry's general
API. Users should puts the binding jars into the install directory of HBase
binaries and we will load them when starting. If no bindings found, we just use
the noop tracer.
Thoughts? Thanks.
> [OpenTracing] Add shaded JaegerTracing tracer to hbase-thirdparty
> -----------------------------------------------------------------
>
> Key: HBASE-23811
> URL: https://issues.apache.org/jira/browse/HBASE-23811
> Project: HBase
> Issue Type: Sub-task
> Components: thirdparty
> Reporter: Wei-Chiu Chuang
> Assignee: Wei-Chiu Chuang
> Priority: Major
>
> JaegerTracing pulls in lots of dependencies. Some, like libthrift (0.13.0)
> conflicts the one ships in HBase (0.12.0).
> Additionally, not everyone may want to use Jaeger.
> I propose to shade JaegerTracing and its dependencies into an uber jar, place
> it as a hbase-thirdparty artifact. As an added benefit, this makes the
> management of tracers in the HBase's dependency tree much easier. Finally, we
> can follow the same suit and provide Zipkin tracer support in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
