-
Notifications
You must be signed in to change notification settings - Fork 976
Propagation - Getter handling of multi-value headers/attributes #433
Copy link
Copy link
Closed
Labels
release:after-gaNot required before GA release, and not going to work on before GANot required before GA release, and not going to work on before GAspec:contextRelated to the specification/context directoryRelated to the specification/context directorytriage:accepted:ready-with-sponsorReady to be implemented and has a specification sponsor assignedReady to be implemented and has a specification sponsor assigned
Milestone
Metadata
Metadata
Assignees
Labels
release:after-gaNot required before GA release, and not going to work on before GANot required before GA release, and not going to work on before GAspec:contextRelated to the specification/context directoryRelated to the specification/context directorytriage:accepted:ready-with-sponsorReady to be implemented and has a specification sponsor assignedReady to be implemented and has a specification sponsor assigned
Type
Projects
Status
Spec - Closed
Some formats (http) allow for a single key to return multiple values. This is used in w3c trace-context which we plan to support:
We don't currently specify this requirement in our spec:
https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/api-propagators.md#getter-argument
As a consequence, we aren't handling that well in java, and likely other languages:
https://github.com/open-telemetry/opentelemetry-java/blob/v0.2.x/api/src/main/java/io/opentelemetry/context/propagation/HttpTextFormat.java#L123
How do we want to handle this? Should we push responsibility for joining them properly to the
Getter, or should the API support returning multiple values?