deepakpanda93 opened a new pull request, #19581: URL: https://github.com/apache/hudi/pull/19581
### Describe the issue this Pull Request addresses The [roadmap page](https://hudi.apache.org/roadmap) had drifted out of date. It still named **1.1.1 (Dec 2025)** as the recent release and listed **1.2.0** as upcoming, months after 1.2.0 shipped in May 2026. Several features on it had already been delivered but were still presented as planned, and every remaining item was targeted at 1.2.0 — a release the same page would have been describing as already out. No issue filed; this is a content refresh. ### Summary and Changelog One file, `website/src/pages/roadmap.md`. It is an unversioned Docusaurus page, so there are no versioned copies. **1. Releases.** *Recent Release(s)* now points at 1.2.0 (May 2026). *Future Releases* becomes: | Release | Timeline | |---|---| | 1.2.1 | Aug 2026 | | 1.3.0 | Sep 2026 | | 2.0.0 | Dec 2026 | The 2.0.0 row also fixes a dangling reference: two *Platform Components* items target 2.0.0, and the table had stopped listing that release at all. **2. Delivered features removed.** All **40** tracked references on the page were checked against GitHub. Five are closed with `state_reason: completed`, and four of those are corroborated by shipped documentation on this site rather than by the label alone: | Section | Feature | Issue | Closed | Corroboration | |---|---|---|---|---| | Storage Engine | Variant type support on Spark 4 | #16851 | 2026-06-25 | `VARIANT` documented in `sql_ddl.md` | | Storage Engine | Vector search index | #16852 | 2026-05-02 | `VECTOR(dim[, elementType])` documented | | Storage Engine | Bitmap index | #16853 | 2026-06-25 | `BITMAP` a valid expression-index type since 1.0.0 | | Storage Engine | NBCC for MDT writes | #17305 | 2026-06-25 | — | | Programming APIs | Support of verification with multiple event_time fields | #15325 | 2026-06-25 | `hoodie.table.ordering.fields` (plural) ships it | The other **35** are genuinely open and were left alone. Worth noting one that deliberately stayed: *Hudi Reverse streamer* tracks #9040, which **is merged** — but that PR only claims the RFC-70 number, it does not deliver the feature. A "merged means done" sweep would have removed it wrongly. **3. Retargeting.** The 21 rows still aimed at 1.2.0 now target **1.2.1**, since 1.2.0 shipped without them. Rows targeting 1.3.0 (2), 2.0.0 (2) and the Presto/Trino release trains (4) are unchanged. Matching was done on the Target Release column specifically, so the *Recent Release* link and the *Future Releases* table were structurally excluded rather than merely avoided — `1.2.0` now appears exactly once in the file, in the Recent Release link. **4. Front matter.** `last_modified_at` bumped per `AGENTS.md`. Being straightforward about this one: it renders nowhere on the page, and no previous roadmap commit has ever bumped it, so it is convention compliance rather than a functional change. Happy to drop it if reviewers would rather keep the diff to content. ### Verification `npm run build` passes with the warning set **byte-identical** to a baseline built from the same base commit, and the roadmap appears nowhere in the warning output. `/roadmap` renders all six tables (38 rows) with all seven headings, none of the five removed features reappear, and the retargeted cells render as `1.2.1`. One thing worth recording for anyone previewing this locally: `npm run serve` returns **404** for `/releases/release-1.2`, which makes the updated Recent Release link look broken. It is not. The built page exists with canonical `https://hudi.apache.org/releases/release-1.2` and carries the `release-120` anchor, and in production that URL 301s to `/releases/release-1.2/` and returns 200 with the anchor present. It is a trailing-slash quirk of the local static server — the previous `/releases/release-1.1#release-111` link behaves identically and has been live for months. ### What was deliberately left alone Three pre-existing issues are visible in the diff and are **not** fixed here, to keep this a content refresh: - Two rows have link text disagreeing with the target: *Simplification of engine integration* displays `#17044` but links to `issues/16857`, and *Syncing as non-partitioned tables* displays `#17045` but links to `issues/16858`. Both hrefs resolve to real open issues with matching titles, so only the labels are wrong. - Four rows point at closed-unmerged RFC PRs (RFC-43 #4309, RFC-36 #4718, RFC-59 #6382, RFC-62 #6600). Three pair the RFC with a still-open umbrella issue, so the work is alive; **Diagnostic Reporter** has only the closed RFC-62 PR behind it, with nothing open — worth deciding whether it belongs on a forward-looking roadmap. - The *Default Java 17 support* row contains literal tab characters in two cells. ### Impact Documentation only. No code, config, or behaviour change. ### Risk Level none ### Documentation Update This PR is the documentation update — the roadmap page, https://hudi.apache.org/roadmap. ### Contributor's checklist - [x] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [x] Enough context is provided in the sections above - [x] Adequate tests were added if applicable -- 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]
