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

   ### Describe the issue this Pull Request addresses
   
   Several links in the documentation are broken or outdated. A link scan 
across the docs surfaced internal links pointing to renamed pages (returning 
404s), external links to pages that have moved or been deprecated, and a 
stack-trace class reference that was mistakenly formatted as a (broken) 
hyperlink. This PR fixes those so readers no longer hit dead links.
   
   ### Summary and Changelog
   
   Fixes broken and outdated links across the documentation. No content or 
behavior changes beyond the corrected links/formatting.
   
   Detailed changelog:
   
   - docs/compaction.md: updated /docs/file_layouts/ to /docs/storage_layouts/ 
(the page was renamed).
   - docs/s3_hoodie.md: updated /docs/hoodie_cleaner to /docs/cleaning (the 
page was renamed).
   - docs/comparison.md: replaced the dead Flink RocksDB state-backend link 
(ci.apache.org) with the current nightlies.apache.org URL.
   - docs/sql_queries.md: updated the Doris Hudi Catalog link to the current 
Doris 3.x docs path.
   - docs/troubleshooting.md: rendered kafka.utils.Utils$.read as inline code 
instead of a broken hyperlink.
   
   ### Impact
   
   Readers get working links instead of 404s. No public API, config, behavior, 
or performance impact.
   
   ### Risk Level
   
   none
   
   ### Documentation Update
   
   This PR is the documentation update. No new feature, config, or user-facing 
behavior is introduced, so no further docs changes are required.
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [ ] 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