yuqi1129 opened a new issue, #13945: URL: https://github.com/apache/gravitino/issues/13945
### Version main branch ### Describe what's wrong Two JDBC property paths silently ignore user input: 1. `jdbc.pool.max-wait-ms` is defined in `JdbcConfig`, but is absent from the catalog property metadata and the forwarding allowlist. A canonical value such as `1234` is dropped before pool initialization, leaving the effective wait at `30000` ms. 2. MySQL accepts undeclared table properties during create/alter validation, then silently drops them during JDBC property mapping. For example, `ROW_FORMAT`, `ENGINE`, and misspelled keys do not produce an actionable error. The declared MySQL properties `engine` and `auto-increment-offset` are intentionally immutable. Unknown keys do not bypass this rule through the normal catalog path: they are filtered before SQL generation. ### Error message and/or stacktrace There is no error for these ignored inputs. Observed pool configuration: `jdbc.pool.max-wait-ms=1234` results in an effective maximum wait of `30000` ms. An unknown MySQL property produces no corresponding table-option change. ### How to reproduce 1. Create a JDBC catalog with `jdbc.pool.max-wait-ms=1234` and inspect the initialized connection pool's maximum wait. 2. Create a MySQL table with an undeclared property such as `ROW_FORMAT=DYNAMIC`, or alter an existing table with that property. 3. Observe that the unknown property is silently discarded instead of being rejected by name. ### Additional context The pool setting needs both metadata registration and forwarding. MySQL should reject unsupported user property names before DDL, retain the existing immutable-property policy and internal metadata handling, and validate supported SQL option values according to their declared types. Other catalogs' custom-property behavior should remain unchanged. -- 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]
