deepakpanda93 commented on issue #15243: URL: https://github.com/apache/hudi/issues/15243#issuecomment-5325045124
This issue was reviewed as part of the JIRA-migrated backlog triage and is being closed as stale. The description is a placeholder rather than a task: *"After the HUDI-83 issue fixes the hive timestamp problem, we need to track whether Presto/Trino can also support this. The test/fix will start after the HUDI-83 issue is merged, and it is planned to complete the test of relevant functions and problem repair before version 0.12 release."* It names no test, no query, and no expected result, and its start condition is another ticket landing. On that gate, a correction worth stating: the Hudi-side Hive timestamp support this was waiting on did ship. `HiveSyncConfig.java:62` declares `HIVE_SUPPORT_TIMESTAMP_TYPE` and applies it at `:200`, and it is present when the file is read at `release-1.2.0`. So the blocker is long gone under a different JIRA key - what never happened is the Presto/Trino verification this ticket exists to track. And 0.12 shipped in August 2022. The JIRA last moved 2023-03-10 and no commit or PR carries HUDI-4274. To be clear, this is being closed as unactionable, not as fixed - I am not claiming Hive timestamp handling works correctly in Trino. Useful successor context: the Trino connector has since been migrated into this repository (`c3c936790727`, 2026-07-26, RFC-105, PR #18837, the `hudi-trino/` module - master-only, not yet in 1.1.0 or 1.2.0). Timestamp behaviour is now testable in-tree, so if there is a real defect, please file it against `hudi-trino/` with a failing query. -- 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]
