Include MultiValueHeaders in DefaultTraceExtractor#202
Closed
jo-me wants to merge 1 commit into
Closed
Conversation
Signed-off-by: Jochen.Mehlhorn <jochen.mehlhorn@mercedes-benz.com>
Contributor
|
this change has been addressed in this pr |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What does this PR do?
This PR merges MultiValueHeader fields with the normal Header fields in the DefaultTraceExtractor
Motivation
current ddlambda tries to read headers from
headerswhile in our case they are passed asmultiValueHeadersTesting Guidelines
local fork
Additional Notes
partly fixes #189 (in combination with PR #201)
Types of changes
Checklist
The program was tested solely for our own use cases, which might differ from yours.
Jochen Mehlhorn jochen.mehlhorn@mercedes-benz.com, Mercedes-Benz Tech Innovation GmbH
Provider Information