Fixed handling of wrong key when text embedded format is used by the producer #880
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 embedded format in the bridge is representative for both key and value.
With the new added
text
embedded format, there is check on the value only while it should be the same for the key.Currently, if the producer uses
text
embedded format but sends a JSON key, the message is accepted but the consumer gets an empty key on the other side. This PR fixes the issue by rejecting the message having a wrongly formatted key (in JSON).