This repository has been archived by the owner on Jan 24, 2024. It is now read-only.
Fix PulsarEntryFormatter not handle null value correctly #305
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.
Fixes #299
PulsarEntryFormatter
doesn't handle null value correctly now. If a message with null value was sent by a producer, the consumer will receive a message with an empty string.This PR fixes the bug and adds to tests to verify KoP could handle the null value no matter what the entry format is.