yuqi1129 opened a new issue, #14642: URL: https://github.com/apache/gravitino/issues/14642
### Version main branch ### Describe what's wrong A long-lived Spark JDBC catalog retains its original connection configuration and credentials. Zone-free PostgreSQL timestamps are exposed as instants and shift with Spark's session time zone. String operations can use source collation after pushdown, changing query results; pushed binary literals can produce invalid SQL. Separately, Trino repeatedly materializes every column inside its column loop, and unsupported schema rename appears as an internal error. ### Error message and/or stacktrace Query results shift or change after pushdown; binary SQL can contain Java array text, and schema rename reports an internal error. ### How to reproduce 1. Alter or recreate a JDBC catalog while keeping a Spark session open, then query it again. 2. Read a PostgreSQL timestamp without time zone under UTC and America/Los_Angeles. 3. Compare string min/max and ORDER BY LIMIT with unpushed evaluation on a linguistically collated source; filter a bytea column with X'01'. 4. Describe a 1000-column table through Trino, and try ALTER SCHEMA RENAME. ### Additional context Affected Spark tables transfer more data: the conservative table-level policy also disables numeric pushdown on a table with a sensitive column. Catalog checks add driver-side server requests and do not revoke already planned/running executor work or cached results. Custom type converters must opt into NTZ handling, and custom table wrappers must pass the catalog guard. The standard JDBC wrapper and PostgreSQL were runtime-tested; other provider-specific adapters require their own validation. No API migration, new dependency, or source schema change is added. -- 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]
