数据目录内容缺失

[lstming]

path: https://doris.apache.org/zh-CN/docs/4.x/connection-integration/mysql-proto#3-%E9%AA%8C%E8%AF%81%E7%99%BB%E5%BD%95

[1. 引入 JDBC 驱动]
[2. 编写连接代码]
[3. 常用 JDBC URL 参数]
[4. 初始化会话变量（可选）]

相对应的内容缺失！！！

[zclllyybb]

Breakwater-GitHub-Analysis-Slot: slot_b16f5d229dea

Initial analysis:

This looks like a documentation rendering/navigation issue, not missing source content.

I checked the current public issue, the live 4.x Chinese page, and the current apache/doris-website upstream master source. In the source file i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/connection-integration/mysql-proto.mdx, the reported Java/JDBC sections are present under the Java tab:

• 1. 引入 JDBC 驱动
• 2. 编写连接代码
• 3. 常用 JDBC URL 参数
• 4. 初始化会话变量（可选）

The live rendered page also contains those headings, but they are inside a Docusaurus TabItem value="java", while the default active tab is MySQL CLI. The page-level table of contents still exposes headings from the inactive Java tab. When a user clicks those TOC entries while the default MySQL CLI tab is active, the anchor points to content inside a hidden tab panel, so the page appears to have missing content.

Recommended next step:

1. Treat this as a website/docs navigation bug for tabbed content.
2. For this page, either remove tab-internal ### headings from the page TOC, for example by setting the page TOC to only include stable top-level headings, or restructure the tab content so hidden-tab headings are not collected by the global TOC.
3. If a site-wide fix is preferred, add custom tab/anchor handling so navigating to an anchor inside a TabItem activates the owning tab, or filter the TOC to only include currently visible tab content.
4. Validate both Chinese and English 4.x pages, since the English 4.x source has the same tab/heading structure.

Useful confirmation steps after a fix:

• Open /zh-CN/docs/4.x/connection-integration/mysql-proto/.
• Click the TOC entries for 1. 引入 JDBC 驱动, 2. 编写连接代码, 3. 常用 JDBC URL 参数, and 4. 初始化会话变量（可选）.
• Confirm the corresponding Java tab content is visible, not hidden behind the default MySQL CLI tab.

Missing information from the report is only the browser/device details. The current source and live HTML are already sufficient to reproduce the apparent missing-content behavior.

[zclllyybb]

Breakwater-GitHub-Analysis-Slot: slot_b16f5d229dea

Preliminary triage:

The reported content does not appear to be missing from the 4.x Chinese documentation source. The Java content exists in i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/connection-integration/mysql-proto.mdx under the Java tab, including:

• 1. 引入 JDBC 驱动
• 2. 编写连接代码
• 3. 常用 JDBC URL 参数
• 4. 初始化会话变量（可选）

What looks wrong is the rendered page navigation behavior. The page opens with the MySQL CLI tab active, but the right-side "本页导航" still includes headings from the hidden Java tab. On the live page HTML, the Java tab panel is present but rendered as a hidden tab panel, while the TOC still links to its headings. This makes the Java sections look like missing content when the user is currently viewing the MySQL CLI tab around #3-验证登录.

Evidence checked:

• The issue screenshot matches the live page state: MySQL CLI content is visible, while Java headings are listed in the right-side TOC.
• The 4.x Chinese MDX source contains the Java section bodies and examples.
• The live HTML contains the Java tab panel and its content, but the panel is hidden until the Java tab is selected.
• The custom docs TOC path appears to render Docusaurus useDoc().toc directly through TOCItems, so it does not filter headings by the currently active tab or switch tabs when a TOC/hash target is inside an inactive tab.

Suggested next steps for maintainers:

1. Treat this as a documentation UX/rendering issue, not as absent translated content.
2. Decide the expected behavior for headings inside tabs across the docs site:
   • either exclude inactive-tab headings from the page TOC,
   • or make TOC/hash navigation activate the tab that owns the target heading.
3. For this page specifically, a content-level workaround would be to avoid h3 headings inside TabItem content, or split each client example into separate sections/pages if those headings should remain globally navigable.
4. Add a regression check for direct links such as /zh-CN/docs/4.x/connection-integration/mysql-proto#1-引入-jdbc-驱动 and /zh-CN/docs/4.x/connection-integration/mysql-proto#3-常用-jdbc-url-参数 from a cold page load.

Missing information:

• Maintainer preference for global TOC behavior on tabbed documentation pages.
• Browser and viewport details from the reporter, in case there is an additional click/scroll issue beyond the confirmed hidden-tab TOC mismatch.