open-telemetry / open-telemetry/opentelemetry-java
Have W3C Baggage size limit implemented yet?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 58
Description
Is your feature request related to a problem? Please describe.
W3C Baggage (https://www.w3.org/TR/baggage/) section 3.2.2 specified baggage size limit:
"A platform MUST propagate all list-members including any list-members added by the platform if the resulting baggage-string would be 8192 bytes or less. If the resulting baggage-string would be greater than 8192 bytes, some list-members MAY be dropped until the resulting baggage-string is 8192 characters or less."
Describe the solution you'd like
Does the current Baggage implementation implemented this baggage limit requirement?
Describe alternatives you've considered
N/A
Additional context
None
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
The issue names no files or tests. Start by locating the Java SDK's Baggage implementation and propagation tests, then compare current behavior with section 3.2.2 of the W3C Baggage specification. Done means establishing whether the 8192-byte limit is implemented and, if not, defining and testing the required behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100