Add support for LinkedHashMap in record value #218
Merged
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.
Description
This pull request addresses an issue where the HTTP Connector for Apache Kafka does not support
LinkedHashMap
as the record value, leading to errors when used in conjunction with Single Message Transforms (SMTs) that returnLinkedHashMap
. The specific error message is: "Record value must be String, Schema Struct, or HashMap, but LinkedHashMap is given."This issue has specifically been encountered with certain SMTs from Confluent, such as
io.confluent.connect.transforms.Filter
, which can utilize LinkedHashMap in ways that the HTTP Connector previously could not handle.Changes Made
LinkedHashMap
as a valid record value.Testing
LinkedHashMap
.How to Verify
LinkedHashMap
as the record value without generating errors.Checklist