-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
Debezium Postgres 3.0.8
What is the connector configuration?
{
"database.dbname": "mydb",
"database.hostname": "<HOSTNAME>",
"database.password": "<PASSWORD>",
"database.port": "5432",
"database.user": "postgresadmin",
"name": "myconnector",
"publication.name": "dbz_publication",
"slot.name": "debezium",
"snapshot.mode": "initial",
"table.include.list": "public.*",
"tasks.max": "1",
"topic.prefix": "mydb-prod"
}
What is the captured database version and mode of deployment?
(E.g. on-premises, with a specific cloud provider, etc.)
RDS Postgres v14
What behavior do you expect?
Either both the column should be stored and remain accessible or the connector should error out in the initial phase.
What behavior do you see?
The connector throwing IndexOutOfBoundsException on case-insensitive duplicates.
Do you see the same behaviour using the latest released Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
Yes.
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
org.apache.kafka.connect.errors.ConnectException: An exception occurred in the change event producer. This connector will be stopped. at io.debezium.pipeline.ErrorHandler.setProducerThrowable(ErrorHandler.java:67) at io.debezium.connector.v2.postgresql.PostgresStreamingChangeEventSource.execute(PostgresStreamingChangeEventSource.java:197) at io.debezium.connector.v2.postgresql.PostgresStreamingChangeEventSource.execute(PostgresStreamingChangeEventSource.java:50) at io.debezium.pipeline.ChangeEventSourceCoordinator.streamEvents(ChangeEventSourceCoordinator.java:334) at io.debezium.pipeline.ChangeEventSourceCoordinator.executeChangeEventSources(ChangeEventSourceCoordinator.java:213) at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:153) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1583) Caused by: java.lang.IndexOutOfBoundsException: Index 30 out of bounds for length 30 at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:100) at java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:106) at java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:302) at java.base/java.util.Objects.checkIndex(Objects.java:385) at java.base/java.util.ArrayList.get(ArrayList.java:427) at java.base/java.util.Collections$UnmodifiableList.get(Collections.java:1502) at io.debezium.connector.v2.postgresql.connection.pgoutput.PgOutputMessageDecoder.resolveColumnsFromStreamTupleData(PgOutputMessageDecoder.java:727) at io.debezium.connector.v2.postgresql.connection.pgoutput.PgOutputMessageDecoder.decodeDelete(PgOutputMessageDecoder.java:509) at io.debezium.connector.v2.postgresql.connection.pgoutput.PgOutputMessageDecoder.processNotEmptyMessage(PgOutputMessageDecoder.java:212) at io.debezium.connector.v2.postgresql.connection.AbstractMessageDecoder.processMessage(AbstractMessageDecoder.java:41) at io.debezium.connector.v2.postgresql.connection.PostgresReplicationConnection$1.deserializeMessages(PostgresReplicationConnection.java:906) at io.debezium.connector.v2.postgresql.connection.PostgresReplicationConnection$1.readPending(PostgresReplicationConnection.java:898) at io.debezium.connector.v2.postgresql.PostgresStreamingChangeEventSource.processMessages(PostgresStreamingChangeEventSource.java:243) at io.debezium.connector.v2.postgresql.PostgresStreamingChangeEventSource.execute(PostgresStreamingChangeEventSource.java:194)\n\t... 9 more\n"
How to reproduce the issue using our tutorial deployment?
Table with duplicate case-insesitive columns duration and "Duration"
Implementation ideas
Fail the connector when the relation message for the duplicate column is sent.
