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

Missing Kafka Connect Configuration - Debezium Specific #1685

Open
Argonus opened this issue Mar 18, 2024 · 2 comments
Open

Missing Kafka Connect Configuration - Debezium Specific #1685

Argonus opened this issue Mar 18, 2024 · 2 comments
Labels
wait for reply Need more information from reporter

Comments

@Argonus
Copy link
Contributor

Argonus commented Mar 18, 2024

Overview

Some of the Debezium Kafka Connect configurations are missing in AKHQ. It looks like all missing entries are the ones that have been added as breaking changes between versions v1.4 and v2.4

Setup

Debezium Version: v2.4
Kafka Connect Version: v7.4.2
AKHQ Version: v0.24.0

Example Missing Entries

It looks like they all are from topic group.

  topic.heartbeat.prefix (renamed from heartbeat.topics.prefix)
  topic.creation.enabled
  topic.creation.default.partitions
  topic.creation.default.replication.factor

Help

I can help with adding new missing config options, but I can't find any configuration in this repo. Shouldn't it be autoloaded somehow, as the older custom Debezium configuration is working?

@github-project-automation github-project-automation bot moved this to Backlog in Backlog Mar 18, 2024
@Argonus Argonus changed the title Missing Connect Configuration Missing Kafka Connect Configuration - Debezium Specific Mar 18, 2024
@AlexisSouquiere
Copy link
Collaborator

I'm not really familiar with the connect definitions feature but for me yes all the metadata are loaded automatically here:

ConnectorsWithExpandedMetadata unfiltered = this.kafkaModule
.getConnectRestClient(clusterId)
.get(connectId)
.getConnectorsWithAllExpandedMetadata();

I don't have time on my side but maybe you should try with the dev branch where the connect client has been updated

@AlexisSouquiere AlexisSouquiere added the wait for reply Need more information from reporter label May 16, 2024
@Argonus
Copy link
Contributor Author

Argonus commented Jun 4, 2024

Thank you, will take a look at it in next few weeks, as I' finally moved to work on Kafka at my current workplace :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wait for reply Need more information from reporter
Projects
Status: Backlog
Development

No branches or pull requests

2 participants