Fix: Cast exception occurs if function/source/sink type is ByteBuffer #11611
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.
Motivation
If a Pulsar Function/Source/Sink is of type ByteBuffer, an cast exception will occur:
The is because if the function is of type ByteBuffer, the schema to used in the consumer is BYTES, which is not correct
Modifications
Use the correct ByteBuffer schema when the type of the function/source/sink is ByteBuffer
Verifying this change
Added a test
Documentation
No changes necessary
For committer
For this PR, do we need to update docs?
No