open-telemetry / open-telemetry/opentelemetry-java
Encode values for the Jaeger propagator
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 58
Description
As a follow-up of #1549 we may need to support encoded Baggage values too.
As Jaeger has support for both URL-encoded and non-encoded values, how should this be implemented? Should we have two Jaeger propagators, i.e. JaegerPropagator.getEncodedInstance() and JaegerPropagator.getInstance()?
(Also, we may need to add a value for OTEL_PROPAGATORS to support this dual case)
@yurishkuro would you mind advising how to proceed here?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing follow-up issue #1549 and the existing Jaeger propagator behavior for URL-encoded and non-encoded Baggage values. Determine whether separate Jaeger propagators or an OTEL_PROPAGATORS option is the intended design, then confirm the decision with the requested maintainer guidance. Done means the implementation approach and configuration behavior are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100