DanielLeens commented on issue #12751: URL: https://github.com/apache/seatunnel/issues/12751#issuecomment-6145192235
Thanks for validating this against a real Dameng instance. The catalog failure is consistent with current `dev`: `DmdbTypeConverter` handles `TIME WITH TIME ZONE` and `DATETIME WITH TIME ZONE`, but has no `TIMESTAMP WITH LOCAL TIME ZONE` or INTERVAL-family path, so those catalog types reach the unsupported default. A focused PR is welcome. Please keep it to Dameng catalog/type conversion: normalize all reported INTERVAL variants before the switch and map that family to the established string representation, while preserving the database source type. For `TIMESTAMP WITH LOCAL TIME ZONE`, first prove with a row-conversion test what the Dameng JDBC driver returns; then align the logical mapping with the existing timezone-aware contract rather than mapping by name alone. Include catalog coverage for the local-time-zone type and representative year-to-month and day-to-second intervals, plus a value-level regression for the timestamp conversion. Please link the PR here. -- 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]
