You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree, this deprecation is not justified, and can be revisited.
When #1923 was implemented (disclosure: I am the author), there was confusion between the Jaeger propagator and the Jaeger exporter.
Assuming the propagator can exist independently of the exporter, deprecating (later removing) the exporter should not have consequences for the propagator.
marcalff
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Oct 7, 2024
marcalff
added a commit
to marcalff/opentelemetry-cpp
that referenced
this issue
Oct 7, 2024
Is your feature request related to a problem?
The Jaeger propagator is not supported without enabling deprecated code.
Describe the solution you'd like
The Jaeger propagator is deprecated in PR #1923 as part of effort removing / deprecating Jaeger exporter.
But the Jaeger propagator should not be deprecated according to specification: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/context/api-propagators.md#propagators-distribution
The specification lists Jaeger as one of the official propagators.
So we should unmark Jaeger propagator as deprecated.
Describe alternatives you've considered
Additional context
The Jaeger propagator is supported in Java, Go and other SDK without being deprecated.
The text was updated successfully, but these errors were encountered: