Skip to content

KIP-875 - First-class offsets support in Kafka Connect #500

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

Closed
2 tasks done
yeikel opened this issue Jul 24, 2024 · 1 comment
Closed
2 tasks done

KIP-875 - First-class offsets support in Kafka Connect #500

yeikel opened this issue Jul 24, 2024 · 1 comment
Labels
status/triage/completed Automatic triage completed status/triage/manual Manual triage in progress type/feature A brand new feature

Comments

@yeikel
Copy link
Collaborator

yeikel commented Jul 24, 2024

Issue submitter TODO list

  • I've searched for an already existing issues here
  • I'm running a supported version of the application which is listed here and the feature is not present there

Is your proposal related to a problem?

Yes, the ability to use the features introduced in KIP-875 are not exposed in the UI (stop a connector, reset the offset of a stopped connector)

Describe the feature you're interested in

KIP-875 just debuted on Kafka 3.6 and it would be great to be able to leverage this feature using the UI

Provides first-class admin support for offsets in Kafka Connect. KIP-875 Part 1 added endpoints to get offsets and a new STOPPED state for connectors. The alter offsets and reset offsets endpoints have now been added.

Action Description
GET /connectors/{connector}/offsets Retrieve the offsets for a connector; the connector must exist
PATCH /connectors/{connector}/offsets Alter the offsets for a connector; the connector must exist, and must be in the STOPPED state
DELETE /connectors/{connector}/offsets Reset the offsets for a connector; the connector must exist, and must be in the STOPPED state
PUT /connectors/{connector}/pause Pause the connector; the connector must exist

Describe alternatives you've considered

Deleting the connector and re-creating it again with a different name is always an option

Version you're running

2956664

Additional context

Ported from provectus/kafka-ui#4289

@yeikel yeikel added status/triage Issues pending maintainers triage type/feature A brand new feature labels Jul 24, 2024
@kapybro kapybro bot added status/triage/manual Manual triage in progress status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Jul 24, 2024
@yeikel
Copy link
Collaborator Author

yeikel commented Jul 24, 2024

I just realized that #183 was ported over. Not sure why I did not see it when I searched

@yeikel yeikel closed this as completed Jul 24, 2024
@Haarolean Haarolean closed this as not planned Won't fix, can't repro, duplicate, stale Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/triage/completed Automatic triage completed status/triage/manual Manual triage in progress type/feature A brand new feature
Projects
None yet
Development

No branches or pull requests

2 participants