fix: compare kafka header keys case insensitively #804
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
t2t2
reviewed
Sep 27, 2023
t2t2
approved these changes
Sep 27, 2023
Co-authored-by: t2t2 <[email protected]>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OTel JS defines carrier keys as lowercase. b3 propagator attempts to read lowercase keys, but other SDKs (Java) produce headers with mixed case keys, causing split traces - open-telemetry/opentelemetry-js#3150
This works fine in the case of HTTP, where node's http module lowercases all keys, but kafkajs retains the key casing.