[
https://issues.apache.org/jira/browse/HBASE-23811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17244954#comment-17244954
]
ramkrishna.s.vasudevan commented on HBASE-23811:
------------------------------------------------
[~zhangduo]
yes I agree with you. Let the hbase code have only the OpenTelemetry or
OpenTracing APIs only. Let the user decide on the impl.
In our POC we ensured that we used the Open tracing based shims that is
provided by Opentelemetry so that we can still use Opentracing APIs but at the
end of the day it is OpenTelemetry that is working. The idea was that since
already the APIs are OpenTelemetry based you still have Opentracing based
compatability. But when I checked last there was no GA release for
OpenTelemetry.
> [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)
