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

Getting Kafka-headers using the builtin Kafka connector #125

Closed
hariso opened this issue Mar 19, 2024 · 1 comment · Fixed by #126
Closed

Getting Kafka-headers using the builtin Kafka connector #125

hariso opened this issue Mar 19, 2024 · 1 comment · Fixed by #126
Assignees
Labels
feature New feature or request

Comments

@hariso
Copy link
Contributor

hariso commented Mar 19, 2024

Feature description

Discussed in ConduitIO/conduit#1446

Originally posted by morethom March 18, 2024
Hi!

Title says it all, I've been trying to migrate from Kafka-connect to Conduit for our replicators and find myself needing the Kafka headers from the messages coming from the source. I can't seem to find support for that and don't necessarily want to rewrite the kafka connector just for this. As anyone been able to get this data and/or is there plans for futur support.

Thanks!

@hariso hariso added feature New feature or request triage labels Mar 19, 2024
@simonl2002 simonl2002 moved this from Triage to Todo in Conduit Main Mar 19, 2024
@simonl2002
Copy link
Member

Looks like multiple folks want this, and it should be fairly low-effort so pulling it in to current release.
@maximus321
@morethom

@simonl2002 simonl2002 removed the triage label Mar 19, 2024
@hariso hariso moved this from Todo to In Review in Conduit Main Mar 19, 2024
@hariso hariso self-assigned this Mar 19, 2024
@github-project-automation github-project-automation bot moved this from In Review to Done in Conduit Main Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants