SEZ9 commented on issue #12515: URL: https://github.com/apache/seatunnel/issues/12515#issuecomment-6378824584
Thanks for the detailed report. The root cause you describe — DuckDBCatalog inheriting the unimplemented getDropTableSql/getTruncateTableSql/getExistDataSql hooks from AbstractJdbcCatalog — lines up with the three failing modes, and the UnsupportedOperationException/CatalogException details you included are enough to confirm the code path. As discussed above, the save-mode fix depends on the attached-catalog routing work in #12506 so that the catalog qualifier is retained and a same-named local `main` table cannot be dropped or cleared. Once that is merged, a focused follow-up PR implementing these hooks, with real JDBC regressions covering RECREATE_SCHEMA, DROP_DATA and ERROR_WHEN_DATA_EXISTS against a DuckDB file, would be very welcome. <!-- streview-comment:1989 --> -- 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]
