-
Bug
-
Resolution: Unresolved
-
Major
-
2.3.3.Final, 2.4.0.Beta2
-
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?
Debezium Postgres Connector 2.3.0.Final
What is the connector configuration?
"connector.class": "io.debezium.connector.postgresql.PostgresConnector",
"offset.storage": "org.apache.kafka.connect.storage.FileOffsetBackingStore",
"offset.storage.file.filename": "D://offset.txt",
"offset.flush.interval.ms": "1000",
"database.hostname": "xxxx",
"database.port": 5432,
"database.password": "xxx",
"database.dbname": "debezium_test",
"database.server.name": "my-postgres-connector",
"plugin.name": "decoderbufs",
"slot.name": "myslot",
"slot.drop.on.stop": "true",
"snapshot.mode": "never",
"converter.schemas.enable": "false",
"decimal.handling.mode": "string",
"topic.prefix": "test",
"table.include.list": "allcolumnsync.test:allcolumnsync.tz_test"
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
on-premises,postgresql 12
What behaviour do you expect?
I expect that the result is infinity or -infinity when timestamp infinity value or -infinity inserted in postgresql.
What behaviour do you see?
These special values are converted to timestamps with value 9223372036825200000 in case of positive infinity or -9223372036832400000 in case of negative infinity.
Do you see the same behaviour using the latest relesead 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)
<Your answer>
How to reproduce the issue using our tutorial deployment?
1. create table
CREATE TABLE allcolumnsync.test (
id bigserial NOT NULL,
"_timestamp" timestamp(6) NULL,
CONSTRAINT allcolumnsync_test_pkey PRIMARY KEY (id)
)
2. insert value
INSERT INTO allcolumnsync.test(id, "_timestamp") VALUES(1, 'infinity');
INSERT INTO allcolumnsync.test(id, "_timestamp") VALUES(1, '-infinity');
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)
Parse like timestamptz type. I have fixed and tested it.