Change metadata processing for single-byte values of kafka headers #3923
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.
The current processing of single-byte values leads to different types and values of metadata. For example integers =< 9 are forwarded with their ascii value and of type number, values above 9 are forwarded as strings. A byte encoded 2 for example is forwarded as 50 because 50 is the ascii code of 2, while a 12 is forwarded as string of "12" like one would expect. We had to check this in the piplines and cast it to the correct value:
This fix changes the kafka input to propagate every value as string.