nevzheng opened a new issue, #12073: URL: https://github.com/apache/gravitino/issues/12073
### What would you like to be improved? The completed Hive V3 compatibility effort in #12060 deliberately left timestamp behavior unchanged. Hive values can carry nanosecond fractions, but Hive Metastore type metadata is unparameterized, and supported Hive versions do not expose identical timezone semantics. The current Gravitino converter maps timezoneless `timestamp(p)` to Hive `timestamp` without proving that precision 9 is preserved end to end, while timezone-aware timestamps retain their pre-existing rejection behavior. This requires a separate compatibility decision rather than a local converter-only change. ### How should we improve? - Reproduce create/write/read behavior on the supported Hive 2.3.9 and 3.1.3 baselines. - Test `timestamp(6)`, `timestamp(9)`, `timestamp_tz(6)`, and `timestamp_tz(9)` through Gravitino, Hive Metastore, and the actual engine value path. - If precision and timezone semantics round-trip faithfully, document and test the supported mapping. - Otherwise, reject the unsupported form with `IllegalArgumentException` before Hive Metastore mutation. - Preserve the completed Variant, Unknown/Null, Geometry, and Geography outcomes from #12060. - Update `docs/apache-hive-catalog.md` with the final timestamp contract. **Related** - Epic: #12056 - Completed Hive compatibility: #12060 - Native nanosecond timestamp foundation: #11962 - Timestamp compatibility discussion: #11936 -- 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]
