This is an automated email from the ASF dual-hosted git repository.

jojochuang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ozone-site.git


The following commit(s) were added to refs/heads/master by this push:
     new a273c7953 HDDS-14980. Fix broken links in "Who Uses Ozone?" page. 
(#432)
a273c7953 is described below

commit a273c79532b76054964118ac805e518e24db01cb
Author: Chi-Hsuan Huang <[email protected]>
AuthorDate: Tue May 19 15:07:32 2026 +0800

    HDDS-14980. Fix broken links in "Who Uses Ozone?" page. (#432)
---
 .../2026-01-30-apache-ozone-best-practices-at-didi.md |   2 +-
 src/pages/community/who-uses-ozone.md                 |   4 ++--
 static/ApacheOzoneBestPracticesAtDidi.pdf             | Bin 0 -> 5642945 bytes
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/blog/2026-01-30-apache-ozone-best-practices-at-didi.md 
b/blog/2026-01-30-apache-ozone-best-practices-at-didi.md
index 5b634d963..fa949b316 100644
--- a/blog/2026-01-30-apache-ozone-best-practices-at-didi.md
+++ b/blog/2026-01-30-apache-ozone-best-practices-at-didi.md
@@ -5,7 +5,7 @@ authors: ["rich7420", "apache-ozone-community", "slfan1989", 
"whbing", "jianghua
 tags: [user-stories, performance, erasure-coding, scale]
 ---
 
-Guest post by the Didi Engineering Team. For the full story with detailed 
slides, see [Apache Ozone Best Practices at Didi 
(PDF)](https://ozone.apache.org/assets/ApacheOzoneBestPracticesAtDidi.pdf).
+Guest post by the Didi Engineering Team. For the full story with detailed 
slides, see [Apache Ozone Best Practices at Didi 
(PDF)](/ApacheOzoneBestPracticesAtDidi.pdf).
 
 As Didi's volume of unstructured data surged into the hundreds of petabytes, 
comprising tens of billions of files, their traditional storage architecture 
faced severe scalability bottlenecks. This post summarizes how they migrated 
from HDFS to Apache Ozone, the optimizations they implemented for 
high-performance reads, and their journey in contributing these improvements 
back to the community.
 
diff --git a/src/pages/community/who-uses-ozone.md 
b/src/pages/community/who-uses-ozone.md
index ec661828a..945d19260 100644
--- a/src/pages/community/who-uses-ozone.md
+++ b/src/pages/community/who-uses-ozone.md
@@ -6,10 +6,10 @@ This page lists organizations that are using Apache Ozone in 
production or for s
 |--------------|---------------------------------------------------------|
 | Tencent      | Data warehouses, Machine Learning Platforms etc: [Tencent 
Cloud Article](https://cloud.tencent.com/developer/article/1667033) |
 | Cloudera     |                                                         |
-| Shopee       | Practices of Ozone at Shopee: [Google Drive 
Link](https://drive.google.com/file/d/1vrUy9K6PlAnNhlaZVJ-6q6cKJIi1QFXA/view) |
+| Shopee       | Practices of Ozone at Shopee: [Apache Ozone Best Practices at 
Shopee (PDF)](/ApacheOzoneBestPracticesAtShopee.pdf) |
 | Preferred Networks | ML Cluster: [A Year with Apache 
Ozone](https://tech.preferred.jp/en/blog/a-year-with-apache-ozone/), [Two Years 
with Apache 
Ozone](https://tech.preferred.jp/en/blog/two-years-with-apache-ozone/) |
 | G-Research   | [G-Research Open-Source](https://opensource.gresearch.co.uk/) 
|
 | Qihoo360     | [WeChat 
Article](https://mp.weixin.qq.com/s/OB_YTlXfDMg6ZfMaYOkn_Q) |
-| DiDi         | [Apache Ozone Best Practices at DiDi 
(PDF)](https://ozone.apache.org/assets/ApacheOzoneBestPracticesAtDidi.pdf) |
+| DiDi         | [Apache Ozone Best Practices at DiDi 
(PDF)](/ApacheOzoneBestPracticesAtDidi.pdf) |
 | Meituan      |                                                         |
 | China Unicom |                                                         |
diff --git a/static/ApacheOzoneBestPracticesAtDidi.pdf 
b/static/ApacheOzoneBestPracticesAtDidi.pdf
new file mode 100644
index 000000000..ca0b2bba1
Binary files /dev/null and b/static/ApacheOzoneBestPracticesAtDidi.pdf differ


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to