Skip to content

Add Kafka Connect artifact publish to release process#15212

Open
rmoff wants to merge 1 commit intoapache:mainfrom
rmoff:confluent-hub-release-process
Open

Add Kafka Connect artifact publish to release process#15212
rmoff wants to merge 1 commit intoapache:mainfrom
rmoff:confluent-hub-release-process

Conversation

@rmoff
Copy link
Contributor

@rmoff rmoff commented Feb 1, 2026

Background

There is currently no prebuilt Iceberg connector for Kafka Connect provided with Iceberg. This can make it more difficult than necessary for users who just want to build pipelines, not run gradle :)

Confluent Marketplace (previously "Confluent Hub") is a long-established platform for the distribution of connectors for Kafka Connect, both open-source and proprietary.
At the moment the 1.9.2 version of the connector has been uploaded to the site by Confluent staff as an ad-hoc process.

There are several existing issues from the community regarding: #10745 #14986 #12516

This PR

(replaces #15113)

This PR does two things:

  1. Includes the Kafka Connect artifact as part of the gradle release command, so it will be published to Maven.
  2. updates the release instructions with details of how to send notice of the new release to Confluent Hub team for inclusion on Confluent Hub

"type": "organization",
"url": "https://iceberg.apache.org",
"username": "iceberg"
"username": "apache"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this change? Is there some reason this needs to be apache as opposed to iceberg?

@@ -0,0 +1,27 @@
# Licensed to the Apache Software Foundation (ASF) under one
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer that we use the name iceberg-sink.properties.template which is more consistent with hive/spark/etc.

2. Confluent will publish to the Marketplace

!!! Note
This step is optional and can be performed by any PMC member after the release is finalized.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why would this be optional? I would think if we're doing updates we always want artifacts updated in the marketplace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants