nevzheng opened a new issue, #12058: URL: https://github.com/apache/gravitino/issues/12058
### Describe the subtask Complete and document the five-family compatibility contract for Flink 1.18 through 1.20. **Compatibility outcomes** - **Nanosecond timestamps:** Round-trip exactly through `TIMESTAMP(9)` and `TIMESTAMP_LTZ(9)`. Reject precision 10 through 12 and unrepresentable offset semantics. - **Variant:** Reject because the supported Flink versions have no faithful equivalent. - **Unknown/Null:** Round-trip nullable Unknown through Flink `NULL`; reject non-null fields. - **Geometry:** Reject with a CRS-preservation explanation. - **Geography:** Reject with a CRS and edge-algorithm preservation explanation. **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 through `TypeUtils` and catalog-create conversion. Verify exact round trips for supported values and pre-mutation rejection for unsupported values in the shared suite and the Flink 1.18, 1.19, and 1.20 suites. **Documentation** `docs/flink-connector/flink-connector.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]
