nsivabalan opened a new pull request, #19070: URL: https://github.com/apache/hudi/pull/19070
## Summary Third post in the MOR-as-architectural-shift blog series. - Walks through Hudi's [async indexing](https://hudi.apache.org/docs/metadata_indexing) design (RFC-45) and explains why the three substrate-level primitives it depends on — stable file-group mutation container, INDEXING as a first-class timeline action, and the two-stage partition lifecycle in table config — only exist because MOR put them in place years earlier. - Contrasts with how Iceberg / Delta would have to approximate the pattern. - Closes the loop with the operational capabilities this unlocks (adding indexes to existing tables without a maintenance window, index re-initialization, staged index rollouts). Series so far: 1. [MOR Isn't a Storage Optimization. It's an Architectural Shift](https://hudi.apache.org/blog/2026/05/14/mor-isnt-a-storage-optimization-its-an-architectural-shift) 2. [Why Metadata Has to Be Mutation-Friendly](https://hudi.apache.org/blog/2026/06/05/why-metadata-has-to-be-mutation-friendly) 3. **Building Indexes on a Moving Target** (this PR) ## Tag allowlist note for reviewer This PR adds `async indexing` to `ALLOWED_TAGS` in `.github/scripts/validate-blog.py`. Per the comment in that file, flagging it here for your approval. Rationale: the entire post is about async indexing, and follow-up posts on related background services will likely reuse the tag. ## Test plan - [x] `python3 .github/scripts/validate-blog.py website/blog/2026-06-25-building-indexes-on-a-moving-target.mdx` passes - [ ] Local site preview renders frontmatter, both inline images, and series links correctly - [ ] Tag filter bar surfaces the post under existing tags (`mor`, `merge on read`, `indexing`, `metadata`, `architecture`, `data lakehouse`) and the new `async indexing` tag -- 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]
