-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
2.6
What is the connector configuration?
connector.class=io.debezium.connector.postgresql.PostgresConnector
plugin.name=pgoutput
binary.handling.mode=hex
What is the captured database version and mode of depoyment?
On-premises postgres
What behaviour do you expect?
When row with toasted bytea column is updated then "__debezium_unavailable_value" should be written.
What behaviour do you see?
Null value is written in kafka record.
Do you see the same behaviour using the latest relesead Debezium version?
Yes
Do you have the connector logs, ideally from start till finish?
2024-03-04 23:00:43,968 WARN Postgres|test_server|0|streaming|postgres Unexpected JDBC BINARY value for field bytea_ with schema Schema{STRING}: class=class java.lang.Object, value=java.lang.Object@5a761c72 [io.debezium.connector.postgresql.PostgresValueConverter]
How to reproduce the issue using our tutorial deployment?
I've impemented a test - RecordsStreamProducerIT#shouldHandleToastedByteaColumnInHexMode
Feature request or enhancement
For feature requests or enhancements, provide this information, please:
Which use case/requirement will be addressed by the proposed feature?
<Your answer>
Implementation ideas (optional)
I've made PR
- links to
-
RHEA-2024:129636 Red Hat build of Debezium 2.5.4 release