hulincup opened a new pull request, #28853:
URL: https://github.com/apache/flink/pull/28853

   ## What & Why
   
   The Hive connector was removed from master in **FLINK-33786** (commit 
`0b99f169`, 2025-02-17). That change deleted the entire 
`docs/content/docs/connectors/table/hive/` directory, but several other 
documents still contained `{{< ref >}}` shortcodes pointing at the removed 
pages, leaving dangling references.
   
   This PR cleans up those dangling references.
   
   ## Changes
   
   - **`docs/connectors/table/overview.md` (EN + ZH)**: Removed the obsolete 
`Apache Hive` entry from the connectors table. The connector no longer exists 
in master, and both its name link and the `Supported Versions` link pointed to 
the deleted `hive/overview` page.
   - **`sql/hive-compatibility/hive-dialect/overview.md` (EN + ZH)**, 
**`sql/catalogs.md` (EN + ZH)**, **`dev/table/modules.md` (EN + ZH)**, 
**`sql/reference/utility/jar.md` (EN + ZH)**, 
**`sql/interfaces/sql-gateway/hiveserver2.md` (EN) / 
`sql/hive-compatibility/hiveserver2.md` (ZH)**, 
**`concepts/sql-table-concepts/versioned_tables.md` (ZH)**: Replaced the broken 
`{{< ref "docs/connectors/table/hive/..." >}}` links with plain text (the 
original link text is retained, only the dead link markup is removed). Valid 
links to other connectors (e.g. JDBC, HBase) and other pages are left untouched.
   
   ## Scope
   
   13 files in total (English + Chinese), purely documentation. No code 
changes. All edits only remove dead `ref` links pointing at the removed 
`connectors/table/hive/` directory; no content is rewritten beyond dropping the 
link markup.
   
   This is a docs-only hotfix following up on FLINK-33786; no JIRA ticket was 
created for the cleanup itself.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
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