DanielLeens commented on issue #11005: URL: https://github.com/apache/seatunnel/issues/11005#issuecomment-4618057039
I checked the current Postgres CDC row-deserialization path in `dev`, and this does look like a real bug rather than a configuration problem. The failing path is that Postgres CDC already reaches the row-schema build stage normally, but `SeaTunnelRowDebeziumDeserializationConverters#createNotNullConverter(...)` still has no `TIMESTAMP_TZ` branch. Once the table contains a PostgreSQL `TIMESTAMP WITH TIME ZONE` column, the code falls through to the default `UnsupportedOperationException`, which matches the stack trace you posted. So the issue is not that `TIMESTAMPTZ` is unknown to SeaTunnel in general. The type already exists in the SeaTunnel type system, and PostgreSQL JDBC paths already support `TIMESTAMP_TZ`. The gap here is specifically in the CDC Debezium row converter. As a temporary workaround, if JSON payloads are acceptable in your pipeline, you can try the compatible Debezium JSON format path instead of the row format. But for the normal row path, this issue is worth tracking as a connector bug. We have labeled this as `bug` and `help wanted` since the reporter did not opt into a PR. A focused fix would be to add `TIMESTAMP_TZ` conversion support in the CDC row converter and cover it with a regression test. cc @yzeng1618 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
