Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Kafka Connect "Single Message Transforms" instead of custom JsonPath #18

Open
berndruecker opened this issue Sep 2, 2019 · 1 comment

Comments

@berndruecker
Copy link
Collaborator

We currently use some JsonPath ourselves to configure where to read certain data from, see e.g. https://github.com/zeebe-io/kafka-connect-zeebe/blob/master/examples/ping-pong/sink.json#L13

That also means we only support Json, not Avro

It would be more Kafka Connect style, if we use the “transforms” (https://docs.confluent.io/current/connect/transforms/index.html) – as in the example in https://www.confluent.io/blog/kafka-connect-deep-dive-jdbc-source-connector

Then we could simply define the expected message format and provide some sample transforms to get there.

@berndruecker berndruecker changed the title Use Kafka Connect Transforms instead of custom JsonPath Use Kafka Connect "Single Message Transforms" instead of custom JsonPath Dec 9, 2019
This was referenced Jul 13, 2021
@ankit-joinwal
Copy link

ankit-joinwal commented Aug 6, 2021

Hi,
As of current version of the zeebe kafka connect plugin, is it possible to use built-in SMT like https://docs.confluent.io/platform/current/connect/transforms/extractfield.html to change the kafka messages being sent from source connector?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants