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

   ### Describe the subtask
   
   Complete and document the five-family compatibility contract for Lance and 
Arrow.
   
   **Compatibility outcomes**
   
   - **Nanosecond timestamps:** Round-trip exactly through Arrow 
`Timestamp(NANOSECOND, null/UTC)`; preserve native non-UTC zones as explicit 
external types.
   - **Variant:** Reject Gravitino Variant before create or overwrite; preserve 
native Arrow extension types losslessly as external types.
   - **Unknown/Null:** Round-trip nullable Unknown through Arrow Null; reject 
non-null fields.
   - **Geometry:** Round-trip exactly through GeoArrow 0.2 WKB plus planar and 
CRS metadata.
   - **Geography:** Round-trip exactly through GeoArrow WKB plus CRS and all 
five edge algorithms.
   
   **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**
   
   Use native Lance schema round trips and verify a rejected Variant overwrite 
leaves the original dataset and metadata intact. Run the three module suites 
and native integration coverage for all five families.
   
   **Documentation**
   
   `docs/lakehouse-generic-lance-table.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