When validation error is raised the messages are too cryptic and do not provide sufficient details required to investigate the problem.

Current error message:

{{2025-02-10 11:03:59,893 ERROR [staging-neptunedb-sourceconnector-reporting|task-0] Error requesting a row value, row: 44, requested index: 44 at position 44 (io.debezium.relational.TableSchemaBuilder) [debezium-sqlserverconnector-staging-neptunedb-sourceconnector-reporting-change-event-source-coordinator] }}

 

{{2025-02-10 11:03:59,932 ERROR [staging-neptunedb-sourceconnector-reporting|task-0] Producer failure (io.debezium.pipeline.ErrorHandler) [debezium-sqlserverconnector-staging-neptunedb-sourceconnector-reporting-change-event-source-coordinator]}}
{{org.apache.kafka.connect.errors.ConnectException: Error while processing event at offset {event_serial_no=1, commit_lsn=00111111:00111111:0002, change_lsn=00111111:00111111:0001}}}
{{    at io.debezium.pipeline.EventDispatcher.dispatchDataChangeEvent(EventDispatcher.java:322)}}
{{    ...}}
{{Caused by: org.apache.kafka.connect.errors.ConnectException: Data row is smaller than a column index, internal schema representation is probably out of sync with real database schema}}
{{    at io.debezium.relational.TableSchemaBuilder.validateIncomingRowToInternalMetadata(TableSchemaBuilder.java:260)}}
{{    ...}}

The error message should identify the table behind schema validation failure.