DanielLeens commented on issue #12542: URL: https://github.com/apache/seatunnel/issues/12542#issuecomment-5931138677
Classification: A / Connector-V2 DuckDB query metadata. Thanks for withdrawing #12543 rather than merging a patch with regressions. I rechecked current `dev` at `d7e9931bea0976547e9730675e7019bbef88ad83`: DuckDB table-path discovery uses its native mapper in `DuckDBCatalog`, but query discovery still inherits `AbstractJdbcCatalog#getTable(String)`, which delegates to the generic `CatalogUtils.getCatalogTable(...)` path. The full query-metadata issue therefore remains unresolved. #12592 is intentionally limited to timestamp aliases and local values; it is related, but it is not a replacement for this issue. Also, #12508 still has a failing Build and has not entered `dev`. Please do not treat its unsigned coverage as delivered and do not revive #12543. A replacement PR should be based on the then-current `dev` and include: native query metadata for DECIMAL precision/scale, TIMESTAMPTZ, UUID/JSON/INTERVAL/HUGEINT, and ARRAY/STRUCT string mapping; regressions for the previously working `TIMESTAMP_S`/`TIMESTAMP_MS`/`TIMESTAMP_NS` aliases and unsigned boundaries; proof that table-path discovery is unchanged; and a query-based Source regression in addition to catalog tests. Please link that focused replacement here when it is ready. -- 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]
