nevzheng opened a new issue, #12068:
URL: https://github.com/apache/gravitino/issues/12068

   ### Describe the subtask
   
   Complete and document the five-family compatibility contract for Doris.
   
   **Compatibility outcomes**
   
   - **Nanosecond timestamps:** Reject timezoneless precision above 6 and every 
timezone-aware timestamp.
   - **Variant:** Reject because the current MySQL JDBC metadata path reports 
Doris Variant as unknown; retain the explicit external-type escape hatch 
separately.
   - **Unknown/Null:** Reject.
   - **Geometry:** Reject because Doris GEO and string forms do not preserve 
Gravitino CRS column semantics.
   - **Geography:** Reject.
   
   **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 Doris and verify rejection before 
DDL and no table creation. Run focused converter/operation coverage and the 
full connector suite.
   
   **Documentation**
   
   `docs/jdbc-doris-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]

Reply via email to