Upgrade Debezium to a newer version
See original GitHub issuePulsar currently use 1.0.0.Final version of Debezium.
This version of Debezium causes issue when using it with Postgres as describe in here
[debezium-postgresconnector-tiktok-change-event-source-coordinator] ERROR io.debezium.pipeline.ErrorHandler - Producer failure
java.lang.IllegalArgumentException: Invalid identifier:
at io.debezium.relational.TableIdParser$TableIdTokenizer.tokenize(TableIdParser.java:68) ~[debezium-core-1.0.0.Final.jar:1.0.0.Final]
at io.debezium.text.TokenStream.start(TokenStream.java:447) ~[debezium-core-1.0.0.Final.jar:1.0.0.Final]
at io.debezium.relational.TableIdParser.parse(TableIdParser.java:28) ~[debezium-core-1.0.0.Final.jar:1.0.0.Final]
at io.debezium.relational.TableId.parse(TableId.java:39) ~[debezium-core-1.0.0.Final.jar:1.0.0.Final]
at io.debezium.connector.postgresql.PostgresSchema.parse(PostgresSchema.java:236) ~[debezium-connector-postgres-1.0.0.Final.jar:1.0.0.Final]
at io.debezium.connector.postgresql.PostgresStreamingChangeEventSource.lambda$execute$0(PostgresStreamingChangeEventSource.java:133) ~[debezium-connector-postgres-1.0.0.Final.jar:1.0.0.Final]
at io.debezium.connector.postgresql.connection.pgproto.PgProtoMessageDecoder.processMessage(PgProtoMessageDecoder.java:53) ~[debezium-connector-postgres-1.0.0.Final.jar:1.0.0.Final]
at io.debezium.connector.postgresql.connection.PostgresReplicationConnection$1.deserializeMessages(PostgresReplicationConnection.java:412) ~[debezium-connector-postgres-1.0.0.Final.jar:1.0.0.Final]
at io.debezium.connector.postgresql.connection.PostgresReplicationConnection$1.readPending(PostgresReplicationConnection.java:406) ~[debezium-connector-postgres-1.0.0.Final.jar:1.0.0.Final]
at io.debezium.connector.postgresql.PostgresStreamingChangeEventSource.execute(PostgresStreamingChangeEventSource.java:119) ~[debezium-connector-postgres-1.0.0.Final.jar:1.0.0.Final]
at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:99) ~[debezium-core-1.0.0.Final.jar:1.0.0.Final]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_265]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_265]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_265]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_265]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_265]
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Release Notes for Debezium 2.1
Release 2.1.0.Alpha1 (November 10th 2022) · Kafka compatibility · Upgrading · Breaking changes · New features · Fixes · Other changes.
Read more >How do I upgrade my Debezium plug-in version in Kafka ...
I am currently running Debezium 0.9.4 and I want to upgrade it to the latest version 1.6. Do I simply download the jar...
Read more >Debezium Releases Version 2.0 of Its Change Data Capture ...
This latest release requires Java 11 and provides: incremental snapshots that are improved with stopping and pause/resume logic; transaction ...
Read more >Chapter 3. Debezium release notes Red Hat Integration 2022.q1
3.4. New Debezium features. Debezium 1.7 includes the following updates: New deployment mechanism: You can now use AMQ Streams to deploy Debezium connectors...
Read more >Upgrading RDS Postgresql 11.6 to 12.2 - Google Groups
During the upgrade, I will stop my Debezium. ... config and stream data to Kafka from the target RDS (the one with the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@hangc0276 => Yup, I am trying to understand the issue and looking for a fix.
@lxcid => Thanks for the lead…
Hi @yeouchien => I reviewed the code changes of #9036, and looks good to me. Please assign this issue to code author. I will pick up another issue to work on. Thank you.