nevzheng opened a new issue, #12066: URL: https://github.com/apache/gravitino/issues/12066
### Describe the subtask Complete and document the five-family compatibility contract for MySQL. **Compatibility outcomes** - **Nanosecond timestamps:** Reject precision above 6; retain precision-6 `DATETIME` and `TIMESTAMP`. - **Variant:** Reject because MySQL JSON is a narrower contract. - **Unknown/Null:** Reject because MySQL has no concrete null-only column type. - **Geometry:** Reject because current reload cannot preserve CRS and SRID. - **Geography:** Reject because MySQL has no distinct geography semantics. **Acceptance** - Reproduce all five families through the connector's public create/conversion path and its alter/load paths where supported. - A supported mapping must round-trip without losing type identity or parameters. - An unsupported mapping must return `IllegalArgumentException` before external metadata mutation; no fallback to a narrower or opaque type is allowed. - Cover nested types where the connector supports complex columns. - Add focused converter/operation tests and an integration or no-side-effect test appropriate to the connector. - Update the connector documentation with a five-family compatibility matrix and rejection rationale. - Keep implementation commits atomic by connector and type family. **Connector-specific verification** Reproduce all five creates against Docker MySQL and verify each rejects before DDL and leaves no table. Cover exact converter messages and the full connector test suite while retaining precision-6 timestamp behavior. **Documentation** `docs/jdbc-mysql-catalog.md` ### Parent issue #12056 -- 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]
