deepakpanda93 commented on code in PR #19581: URL: https://github.com/apache/hudi/pull/19581#discussion_r3860096657
########## website/src/pages/roadmap.md: ########## Review Comment: Updated in 690984769e44. The two Trino rows claimed MDT support and new index support were still pending Trino work, which per your comment misstates where the work actually sits. They are replaced by a single row: > | Update the Trino Hudi connector to the new shim approach (MDT and index support are complete on the Hudi side) | Trino Release | [#14906](https://github.com/apache/hudi/issues/14906) | Two things I want to flag rather than quietly decide, since "updated accordingly" leaves room for interpretation. **The shim work itself already appears closed.** Checking the refactoring items from the 1.3 planning discussion: [#18780](https://github.com/apache/hudi/issues/18780) is closed as completed, [#18782](https://github.com/apache/hudi/pull/18782) (RFC-105, shim/bundle) is closed, and [#18837](https://github.com/apache/hudi/pull/18837) is closed. So I could not tell from issue state alone whether the remaining work is the OSS-connector update on the Trino side, which would live outside this repo, or something still open here. I kept the umbrella [#14906](https://github.com/apache/hudi/issues/14906) as the tracking link because it is still open, but if there is a better issue for the OSS-connector update I will point the row at it. **The Presto rows are untouched.** Your comment was on the Trino line, and the Presto entries still reference open issues ([#14992](https://github.com/apache/hudi/issues/14992), [#15246](https://github.com/apache/hudi/issues/15246), [#15319](https://github.com/apache/hudi/issues/15319)), so I did not assume the same reframing applies there. Note though that the 1.3 discussion lists "Hudi 1.2 upgrade in Presto connector" while the page still says "Support Hudi **1.0** release in Presto Hudi Connector" — that looks stale in the same way, and I am happy to update it if you confirm the intent. -- 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]
