docs(roadmap): refresh releases, drop delivered items, retarget to 1.2.1 #19581
+26
−30
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -1,6 +1,6 @@ | |||||||||||
| --- | |||||||||||
| title: Roadmap | |||||||||||
| last_modified_at: 2026-08-11T15:28:37+05:30 | |||||||||||
| --- | |||||||||||
|
|
|||||||||||
| # Roadmap | |||||||||||
|
|
@@ -11,53 +11,49 @@ down by areas on our [stack](/docs/hudi_stack). | ||||||||||
|
|
|||||||||||
| ## Recent Release(s) | |||||||||||
|
|
|||||||||||
| [1.2.0](/releases/release-1.2#release-120) (May 2026) | |||||||||||
|
|
|||||||||||
| ## Future Releases | |||||||||||
|
|
|||||||||||
| | Release | Timeline | | |||||||||||
| |---------|-----------| | |||||||||||
| | 1.2.1 | Aug 2026 | | |||||||||||
| | 1.3.0 | Sep 2026 | | |||||||||||
| | 2.0.0 | Dec 2026 | | |||||||||||
|
|
|||||||||||
| ## Storage Engine | |||||||||||
|
|
|||||||||||
| | Feature | Target Release | Tracking | | |||||||||||
| |------------------------------------------------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | |||||||||||
| | Introduce `.abort` state in the timeline | 1.2.1 | [#16609](https://github.com/apache/hudi/issues/16609) | | |||||||||||
| | Non-blocking updates during clustering | 1.2.1 | [#14611](https://github.com/apache/hudi/issues/14611) | | |||||||||||
| | Enable partial updates for CDC workload payload | 1.2.1 | [#16354](https://github.com/apache/hudi/issues/16354) | | |||||||||||
| | Schema tracking in metadata table | 1.2.1 | [#14397](https://github.com/apache/hudi/issues/14397) | | |||||||||||
| | Index abstraction for writer and reader | 1.2.1 | [#16903](https://github.com/apache/hudi/issues/16903) | | |||||||||||
| | New abstraction for schema, expressions, and filters | 1.2.1 | [RFC-88](https://github.com/apache/hudi/pull/12795) | | |||||||||||
| | Streaming CDC/Incremental read improvement | 1.2.1 | [#14916](https://github.com/apache/hudi/issues/14916) | | |||||||||||
| | Supervised table service planning and execution | 1.2.1 | [RFC-43](https://github.com/apache/hudi/pull/4309), [#15196](https://github.com/apache/hudi/issues/15196) | | |||||||||||
| | General purpose support for multi-table transactions | 1.2.1 | [#16181](https://github.com/apache/hudi/issues/16181) | | |||||||||||
| | Supporting different updated columns in a single partial update log file | 1.2.1 | [#16854](https://github.com/apache/hudi/issues/16854) | | |||||||||||
| | CDC format consolidation | 1.2.1 | [#16429](https://github.com/apache/hudi/issues/16429) | | |||||||||||
| | Time Travel updates, deletes | 1.3.0 | [#16855](https://github.com/apache/hudi/issues/16855) | | |||||||||||
| | Unstructured data storage and management | 1.3.0 | [#16856](https://github.com/apache/hudi/issues/16856)| | |||||||||||
|
|
|||||||||||
| ## Programming APIs | |||||||||||
|
|
|||||||||||
| | Feature | Target Release | Tracking | | |||||||||||
| |---------------------------------------------------------|----------------|----------------------------------------------------------------------------------------------------------------------------| | |||||||||||
| | New Hudi Table Format APIs for Query Integrations | 1.2.1 | [RFC-64](https://github.com/apache/hudi/pull/7080), [#15194](https://github.com/apache/hudi/issues/15194) | | |||||||||||
| | Snapshot view management | 1.2.1 | [RFC-61](https://github.com/apache/hudi/pull/6576), [#15367](https://github.com/apache/hudi/issues/15367) | | |||||||||||
|
|
|||||||||||
| ## Query Engine Integration | |||||||||||
|
|
|||||||||||
| | Feature | Target Release | Tracking | | |||||||||||
| |---------------------------------------------------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | |||||||||||
| | Default Java 17 support | 1.2.1 | [#16082](https://github.com/apache/hudi/issues/16082) | | |||||||||||
| | Spark datasource V2 read | 1.2.1 | [#15292](https://github.com/apache/hudi/issues/15292) | | |||||||||||
| | Simplification of engine integration and module organization | 1.2.1 | [#16857](https://github.com/apache/hudi/issues/16857) | | |||||||||||
| | End-to-end DataFrame write path on Spark | 1.2.1 | [#16846](https://github.com/apache/hudi/issues/16846), [#15433](https://github.com/apache/hudi/issues/15433) | | |||||||||||
| | Support Hudi 1.0 release in Presto Hudi Connector | Presto Release / Q2 | [#14992](https://github.com/apache/hudi/issues/14992) | | |||||||||||
| | Support of new indexes in Presto Hudi Connector | Presto Release / Q3 | [#15246](https://github.com/apache/hudi/issues/15246), [#15319](https://github.com/apache/hudi/issues/15319) | | |||||||||||
| | MDT support in Trino Hudi Connector | Trino Release / Q2 | [#14906](https://github.com/apache/hudi/issues/14906) | | |||||||||||
|
|
@@ -67,14 +63,14 @@ down by areas on our [stack](/docs/hudi_stack). | ||||||||||
|
|
|||||||||||
| | Feature | Target Release | Tracking | | |||||||||||
| |---------------------------------------------------------------------------------------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------| | |||||||||||
|
Contributor
There was a problem hiding this comment. 🤖 Similar mismatch: the link text reads #17045 but the href resolves to issues/16858. Could be corrected in passing so the visible number matches the link.
Collaborator
Author
There was a problem hiding this comment. Same fix, same direction — the href was right and the label was wrong. e61fb8e.
Relabelled to Build is clean with the warning set byte-identical to a baseline of the same base commit, and a scan of the page confirms zero remaining |
|||||||||||
| | Syncing as non-partitoned tables in catalogs | 1.2.1 | [#16858](https://github.com/apache/hudi/issues/16858) | | |||||||||||
| | Hudi Reverse streamer | 1.2.1 | [RFC-70](https://github.com/apache/hudi/pull/9040) | | |||||||||||
| | Diagnostic Reporter | 1.2.1 | [RFC-62](https://github.com/apache/hudi/pull/6600) | | |||||||||||
| | Mutable, Transactional caching for Hudi Tables (could be accelerated based on community feedback) | 2.0.0 | [Strawman design](https://docs.google.com/presentation/d/1QBgLw11TM2Qf1KUESofGrQDb63EuggNCpPaxc82Kldo/edit#slide=id.gf7e0551254_0_5), [#16072](https://github.com/apache/hudi/issues/16072) | | |||||||||||
| | Hudi Metaserver (could be accelerated based on community feedback) | 2.0.0 | [#15011](https://github.com/apache/hudi/issues/15011), [RFC-36](https://github.com/apache/hudi/pull/4718) | | |||||||||||
|
|
|||||||||||
| ## Developer Experience | |||||||||||
|
|
|||||||||||
| | Feature | Target Release | Tracking | | |||||||||||
| |---------------------------------------------------------|----------------|------------------------------------------| | |||||||||||
| | Clean up tech debt and deprecate unused code | 1.2.1 | [#16859](https://github.com/apache/hudi/issues/16859) | | |||||||||||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖 This retargets ~21 rows that previously pointed at 1.2.0 onto 1.2.1 (Aug 2026), presented as a patch release. Several are substantial features (multi-table transactions, non-blocking updates during clustering, supervised table service planning). It might help to confirm whether major feature work is intended for a patch line, or whether some should move to 1.3.0. @yihua could you confirm the intended targeting?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair question, and I want to be clear about whose call this is: the 1.2.0 → 1.2.1 retarget was a deliberate instruction from the maintainer driving this refresh, not something I inferred. So I have left it as-is rather than second-guess the release plan.
The reason it needed doing at all: those rows all said 1.2.0, which the same page now lists under Recent Release(s) as shipped in May 2026. So before this PR the page claimed 21 features were targeted at a release that had already gone out without them. Moving them to the next dated entry is strictly better than leaving them pointing at the past, whatever the eventual landing release turns out to be.
Your substantive point stands though: 1.2.1 (Aug 2026) reads as a patch line, and items like General purpose support for multi-table transactions, Non-blocking updates during clustering and Supervised table service planning and execution are not patch-sized. If the intent is that these land in 1.3.0 (Sep 2026) and 1.2.1 carries only fixes, then some or all of the 21 should move again. Two of the largest items — Time Travel updates, deletes and Unstructured data storage and management — were already on 1.3.0 and I did not touch them, which is some evidence that 1.3.0 is where feature work is expected.
I have flagged this back to the maintainer. Deferring to @yihua or another committer on the split, and happy to re-target any subset in this PR once someone with visibility into the release plan says which.
One thing worth noting for whoever decides: nothing about the targets is load-bearing for correctness here. Every row's tracking issue was verified open (35 of the 40 references on the page), so the rows themselves are accurate regardless of which release column they sit in.