[
https://issues.apache.org/jira/browse/KAFKA-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822420#comment-15822420
]
ASF GitHub Bot commented on KAFKA-3209:
---------------------------------------
GitHub user shikhar opened a pull request:
https://github.com/apache/kafka/pull/2374
KAFKA-3209: KIP-66: more single message transforms
WIP, in this PR I'd also like to add doc generation for transformations.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shikhar/kafka more-smt
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2374.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2374
----
commit f34cc71c9931ea7ec5dd045512c623196928a2a3
Author: Shikhar Bhushan <[email protected]>
Date: 2017-01-13T20:00:31Z
SetSchemaMetadata SMT
commit 09af66b3f1861bf2a0718aaf79ca1a3bd22adcec
Author: Shikhar Bhushan <[email protected]>
Date: 2017-01-13T21:44:57Z
Support schemaless and rename HoistToStruct->Hoist; add the inverse Extract
transform
commit 022f4920c5f09d068bbf49e47091a1333dc48be2
Author: Shikhar Bhushan <[email protected]>
Date: 2017-01-13T21:51:43Z
InsertField transform -- fix bad name for interface containing config name
constants
commit c5260a718e2f0ade66c4607a4b9c21abda61b90c
Author: Shikhar Bhushan <[email protected]>
Date: 2017-01-13T22:01:25Z
ValueToKey SMT
----
> Support single message transforms in Kafka Connect
> --------------------------------------------------
>
> Key: KAFKA-3209
> URL: https://issues.apache.org/jira/browse/KAFKA-3209
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Reporter: Neha Narkhede
> Assignee: Shikhar Bhushan
> Labels: needs-kip
> Fix For: 0.10.2.0
>
>
> Users should be able to perform light transformations on messages between a
> connector and Kafka. This is needed because some transformations must be
> performed before the data hits Kafka (e.g. filtering certain types of events
> or PII filtering). It's also useful for very light, single-message
> modifications that are easier to perform inline with the data import/export.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)