[
https://issues.apache.org/jira/browse/KAFKA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000069#comment-17000069
]
ASF GitHub Bot commented on KAFKA-9318:
---------------------------------------
piotrsmolinski commented on pull request #7856: KAFKA-9318: added SMT to
extract map values
URL: https://github.com/apache/kafka/pull/7856
The change adds a SMT to extract map entries.
The SMT is counterpart to the existing ExtractField SMT.
The SMT is isolated from other components and simple
unit tests seem to be sufficient.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Kafka Connect. Add map entry value extraction SMT
> -------------------------------------------------
>
> Key: KAFKA-9318
> URL: https://issues.apache.org/jira/browse/KAFKA-9318
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 2.4.0
> Reporter: Piotr Smolinski
> Priority: Major
>
> Currently there is ExtractField SMT available that makes it possible to pull
> specific field from generic JSON or Connect Struct. When Connect Struct with
> a map field is used this approach does not work when given map entry has to
> be extracted.
> Example case: JMS source imports message that has entity correlation key
> inside message property. We want to use the same key for Kafka messages.
> Currently it requires custom SMT coding, while the logic is generic.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
