Upgrade to Debezium 3.2.0.Final #1526
Conversation
Status for workflow
|
| Status | Name | Step | Failures | Logs | Raw logs |
|---|---|---|---|---|---|
| ✖ | Build - JDK 17 | Build with Maven |
Failures | Logs | Raw logs |
Full information is available in the Build summary check run.
Failures
⚙️ Build - JDK 17 #
- Failing: Root module
📦 Root module
✖ Failed to execute goal io.quarkus:quarkus-platform-bom-maven-plugin:0.0.121:invoke-platform-project (build-platform-project) on project quarkus-platform-config: Failed to build the platform project, please consult the errors logged above.
📦 generated-platform-project/quarkus-blaze-persistence/integration-tests/blaze-persistence-examples-quarkus-3-testsuite-base
✖ com.blazebit.examples.quarkus.testsuite.base.QuarkusExampleTest.updatePerson - More details - Source on GitHub
java.lang.RuntimeException: java.lang.ExceptionInInitializerError
at io.quarkus.test.junit.QuarkusTestExtension.throwBootFailureException(QuarkusTestExtension.java:668)
at io.quarkus.test.junit.QuarkusTestExtension.interceptTestClassConstructor(QuarkusTestExtension.java:763)
at java.base/java.util.Optional.orElseGet(Optional.java:364)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Caused by: java.lang.ExceptionInInitializerError
at java.base/java.lang.Class.forName0(Native Method)
|
full stack error: |
|
the version of Hibernate in Debezium has not been changed debezium/debezium@3af4edc |
|
the version of Hibernate used in Quarkus seems to be 7.x although Debezium is on 6.x the upgrade in Quarkus from 6 to 7 has been done with quarkusio/quarkus@e391bea#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8 which means it arrived with Quarkus 3.24.0 |
|
but the upgrade to Debezium 3.1 is already part of Quarkus 3.24.3 and it wasn't a problem 09aa94a |
|
We should maybe consider to hold merge of this PR. It breaks the Camel Debezium components due to However, we're not in an LTS stream here, so I am somewhat more relaxed about it. But Camel Quarkus won't be in alignment with DBZ 3.2.0.Final until either CQ 3.26.0 or 3.27.0 is released (probably next month and beyond).
@apupier The Blaze Persistence test failure is already a known issue related to the Hibernate 7 upgrade & unrelated to this PR. |
On this part, I think we can update the Camel Debezium component as this class was deprecated for quite some time already even without upgrading Debezium to 3.2. it could allow a smoother transition, created apache/camel#18582 |
Ya we haven't had a chance to bump Hibernate to ORM 7. I'll make this a priority in early 3.3 so that we can look at bumping to 3.2.1.Final with backporting that upgrade here. Thanks for the feedback and analysis! |
|
The BlazeBit error is known and not related to Debezium. As for Camel Quarkus, what's your preference you all, should we merge for 3.25 or wait? |
I'm ok with merging this. The Camel core |
|
@jamesnetherton but current main is still |
|
Then unless there's some urgency to have this change merged, lets wait until Camel catches up. |
|
@gsmet, from Debezium's side, we have no preference. The only downside right now is that Debezium (regardless of version we incorporate here) will be broken with ORM 7.x. It's unfortunate but I have already fixed this in Debezium's development branch and will be fixed in the 3.2.1.Final in early August most likely. From our side, we would have fixed this sooner, but sadly with some upgrade blockers with Apicurio, we've been stuck on a prior Quarkus version for longer than desired. |
|
OK, then let's update to 3.2.1 when available and wait for the next round of releases with 3.26 to include this. In any case, let's make sure this situation is sorted out before the next LTS (which will be 3.27). |
No description provided.