SEZ9 commented on issue #12601: URL: https://github.com/apache/seatunnel/issues/12601#issuecomment-5945218007
Thanks for the detailed report and the reproducible steps. The analysis makes sense: the type name for the added column comes from Debezium's `Column.typeName()` and is passed through unquoted and unqualified into the generated `ALTER TABLE ... ADD COLUMN`, so mixed-case, reserved-word, and non-`search_path` type names break. Quoting the type name in the generated DDL looks like a reasonable direction; schema-qualifying it would also require knowing the type's namespace on the source side. To help narrow this down, could you share: - the SeaTunnel version(s) you tested and the PostgreSQL server version; - the full sink-side exception/log for the failing mixed-case range type case; - whether the user-defined types already exist in the sink database with the same name and schema, since the sink does not create the types itself. If you'd like to work on a fix, a PR would be very welcome. <!-- streview-comment:1463 --> -- 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]
