You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2026-03-26-debezium-3-5-cr1-released.adoc
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,6 +62,23 @@ But as we begin to look at moving Debezium Server to be based on the Debezium Qu
62
62
With Debezium 3.5, we have introduced a new compatibility layer that allows running Debezium source connectors that are not natively implemented in the extension framework.
63
63
This provides a solid foundation not only for Debezium Server, but to running any Debezium source connector within Quarkus, as long as using non-native builds is acceptable (https://github.com/debezium/dbz/issues/1612[dbz#1612]).
64
64
65
+
For example, in a Quarkus application to use the Debezium Informix connector, which currently does not have a native build option, you would add the following dependencies:
66
+
67
+
[source,xml]
68
+
----
69
+
<!-- add the Debezium Quarkus Engine -->
70
+
<dependency>
71
+
<groupId>io.debezium</groupId>
72
+
<artifactId>debezium-quarkus-engine</artifactId>
73
+
</dependency>
74
+
75
+
<!-- add the Debezium-ready Connector for your datasource -->
A second-level cache, aka (L2C), and search indexes can boost an application's performance, but the information in these data stores can quickly become stale when changes are made to the data outside the scope of Hibernate ORM.
0 commit comments