[Subtask] Validate JDBC type mappings before table DDL
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 935
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 298
Description
### Describe the subtask
Add shared whole-request preflight validation for JDBC catalogs. This is infrastructure for the seven JDBC connector subtasks, not an additional connector/type-matrix row.
**Scope**
- Validate both create-table overloads before SQL generation or execution.
- Validate the complete alter batch before executing any individual change.
- Provide protected live-connection capability hooks for connector-specific validation.
- Wire custom table-operation implementations, including ClickHouse and OceanBase.
- Preserve deterministic `IllegalArgumentException` messages and the REST invalid-argument response: HTTP 400 and error code 1001.
**Acceptance**
- Reproduce a create request containing an unsupported type.
- Reproduce a mixed alter batch in which a valid change precedes an unsupported add-column.
- Verify no SQL is executed and no partial mutation occurs.
- Run JDBC-common, all seven JDBC connector non-integration suites, and focused server table-operation tests.
- Update the shared relational metadata documentation.
**Documentation**
`docs/manage-relational-metadata-using-gravitino.md`
### Parent issue
#12056
Contributor guide
Assessment
This issue has not been assessed yet.