Remove jaeger exporter

[marcalff]

Fixes #3551

Changes

Please provide a brief description of the changes here.

• Updated CHANGELOG
• Removed the Jaeger exporter and related configuration
• Removed entries from the spec compliance matrix.

[marcalff]

To @open-telemetry/specs-trace-approvers @yurishkuro

This PR removes the Jaeger Exporter from the specification, as it was scheduled for removal in July 2023, as announced by:

• Deprecate jaeger exporters. #2858

[EDIT 2023-06-23: revisited item (1) and (2) per review comments]

(1) In my understanding, now that trace data is no longer exported in Jaeger format (Jaeger can accept OTLP directly), there should no longer be a use case to have a Jaeger Propagator. As a result, this change removes the JaegerPropagator specifications as well.

(1) The Jaeger Propagator specification is unchanged, per clarifications from Yuri.

(2) Also in my understanding, the mapping (specification/trace/sdk_exporters/jaeger.md) from OTLP to Jaeger format is no longer needed, as no code will ever perform this transformation, so the mapping is also removed from the specification.

(2) The mapping (specification/trace/sdk_exporters/jaeger.md) from OTLP to Jaeger format is preserved in the specification.

(3) On a related topic, the specification also mention the Jaeger Remote Sampler. I left the spec for the remote sampler as is, assuming the remote sampler and the export format are orthogonal concerns, i.e., it still makes sense to have remote sampling even when traces are exported in OTLP, not Jaeger, format.

Please let me know if I missed something, in particular in (1), (2) and (3), and I will adjust the patch accordingly.

[yurishkuro]

Jaeger propagator has no relation to the export data format. Once a propagation format is rolled out in a company, changing it is quite expensive and cannot be done without dual writing phase. In contrast, switching export format can be easily done incrementally.

[marcalff]

Jaeger propagator has no relation to the export data format. Once a propagation format is rolled out in a company, changing it is quite expensive and cannot be done without dual writing phase. In contrast, switching export format can be easily done incrementally.

Thanks for the comments.

The PR is now revised as follows:

• the Jaeger Exporter is removed
• the Jaeger Propagator is untouched (previous changes are rolled back)
• the Jaeger Remote Sampler is untouched

Please take another look.

opentelemetry-cpp will also preserve the Jaeger Propagator then.

[mateuszrzeszutek]

🎉