SEZ9 commented on issue #12542: URL: https://github.com/apache/seatunnel/issues/12542#issuecomment-5883122387
Thanks for the detailed report and reproduction. Confirmed scope: `table_path` already goes through the DuckDB converter, so the fix should route the `query` path (ResultSetMetaData) through the same DuckDB type mapper so aliases/expressions get native type names, precision, and scale. Please link the companion PR here so we can track it. Please make sure the PR adds a unit test on `DuckDBCatalog.getTable(String)` (query path) covering DECIMAL(20,0), TIMESTAMPTZ, UUID/JSON/INTERVAL/HUGEINT, and INTEGER[]/STRUCT, and ideally extend the existing DuckDB JDBC IT with a `query`-based source case so the regression is caught end-to-end. One clarification: for LIST/STRUCT mapping to STRING, is that consistent with how the existing DuckDB converter handles these types on the `table_path` path today? If so, please note it in the PR description so reviewers can verify both discovery paths produce identical schemas for the same table. <!-- streview-comment:1403 --> -- 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]
