-
Bug
-
Resolution: Done
-
Major
-
2.2.1.Final
-
None
-
False
-
None
-
False
-
Important
The docker image for debezium/connect:2.2.1.Final is not on dockerhub (https://hub.docker.com/r/debezium/connect/tags?page=1&name=2.2.1) or quay.io (https://quay.io/repository/debezium/connect?tab=tags). Despite the jar being available since 12th May 2023.
Further, the debezium/connect:2.2 seems to reference ENV DEBEZIUM_VERSION=2.2.0.Final (https://hub.docker.com/layers/debezium/connect/2.2/images/sha256-607db44207ac5c666d0ce562e2d15becdd1a2bb7e1de77b2391477488762536b?context=explore) and not 2.2.1.Final. The same applies for the 2.2 tag on quay.io.
What Debezium connector do you use and what version?
v2.2.1.Final
What is the connector configuration?
N/A
What is the captured database version and mode of depoyment?
N/A
What behaviour do you expect?
- Image for debezium/connect:2.2.1.Final to be available on dockerhub or quay.io
- debezium/connect:2.2 to be up to date on dockerhub or quay.io
What behaviour do you see?
- Image for debezium/connect:2.2.1.Final is NOT on dockerhub or quay.io
- debezium/connect:2.2 references older 2.2 version on dockerhub or quay.io
Do you see the same behaviour using the latest relesead Debezium version?
N/A
Do you have the connector logs, ideally from start till finish?
N/A
How to reproduce the issue using our tutorial deployment?
N/A
- links to
-
RHEA-2023:120698 Red Hat build of Debezium 2.3.4 release