yihua opened a new pull request, #20342:
URL: https://github.com/apache/hudi/pull/20342

   ### Describe the issue this Pull Request addresses
   
   JD.com published a write-up of its Flink Forward Asia 2026 talk on unifying 
its Hudi data lake and real-time streams with Apache Fluss, but [the 
original](https://mp.weixin.qq.com/s/uVv9maXyDnObbfjTRoqrzg) is only available 
in Chinese on WeChat. It is a production case study on Hudi at JD's scale 
(5,000+ tables, 700+ PB) and covers the Fluss Tiering Service to Hudi (FIP-24), 
so it is worth having in English on hudi.apache.org.
   
   ### Summary and Changelog
   
   Adds an English translation of the post, following the convention of the 
earlier translated blogs (the JD meetup recap and the Hudi 1.1 Flink deep 
dives): the italic "translated from the original blog in Chinese" note with a 
link to the source, and the images under 
`website/static/assets/images/blog/<post>/`.
   
   - 
`website/blog/2026-10-14-jd-lake-stream-unification-with-fluss-and-hudi.md`: 
the translated post, category `case-study`.
   - 18 slide images with the Chinese text replaced by English in place. The 
conference header banner and the WeChat community QR code from the original are 
dropped.
   - `.github/scripts/validate-blog.py`: adds `apache fluss` to `ALLOWED_TAGS`. 
This new tag needs reviewer approval.
   
   ### Impact
   
   New blog post on the website. No code change.
   
   ### Risk Level
   
   none
   
   ### Documentation Update
   
   This PR is the documentation update.
   
   ### 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
   - [ ] 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]

Reply via email to