Skip to content

Fix broken external documentation links #23163

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wenxiaojie1 wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Fix broken external documentation links #23163

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
06fcae1
Fix broken external documentation link
wenxiaojie1 Jun 29, 2026
f71a855
Fix broken external documentation link
wenxiaojie1 Jun 29, 2026
84160b6
Address documentation style feedback
wenxiaojie1 Jun 29, 2026
929e955
Address documentation style feedback
wenxiaojie1 Jun 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ai/integrations/vector-search-integrate-with-langchain.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ This tutorial demonstrates how to integrate [TiDB Vector Search](/ai/concepts/ve

> **Tip**
>
> You can view the complete [sample code](https://docs.langchain.com/oss/python/integrations/vectorstores/tidb_vector) in LangChain documentation.
> You can view the complete [TiDBVectorStore API reference](https://reference.langchain.com/python/integrations/langchain_community.vectorstores.tidb_vector.TiDBVectorStore/) in LangChain documentation.

@gemini-code-assist gemini-code-assist Bot Jun 29, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

According to the repository style guide, code snippets, class names, and technical identifiers should be enclosed in backticks for clarity.

Suggested change
> You can view the complete [TiDBVectorStore API reference](https://reference.langchain.com/python/integrations/langchain_community.vectorstores.tidb_vector.TiDBVectorStore/) in LangChain documentation.
> You can view the complete [`TiDBVectorStore` API reference](https://reference.langchain.com/python/integrations/langchain_community.vectorstores.tidb_vector.TiDBVectorStore/) in LangChain documentation.
References
  1. Code snippets, command names, options, and paths should be in backticks. (link)


## Prerequisites

Expand Down
2 changes: 1 addition & 1 deletion ticdc/ticdc-debezium.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -781,7 +781,7 @@ The key fields of the preceding JSON data are explained as follows:

### Data type mapping

The data format mapping in the TiCDC Debezium message basically follows the [Debezium data type mapping rules](https://debezium.io/documentation/reference/2.4/connectors/mysql.html#mysql-data-types), which is generally consistent with the native message of the Debezium Connector for MySQL. However, for some data types, the following differences exist between TiCDC Debezium and Debezium Connector messages:
The data format mapping in the TiCDC Debezium message basically follows the [Debezium data type mapping rules](https://debezium.io/documentation/reference/stable/connectors/mysql.html#mysql-data-types), which is generally consistent with the native message of the Debezium Connector for MySQL. However, for some data types, the following differences exist between TiCDC Debezium and Debezium Connector messages:

@gemini-code-assist gemini-code-assist Bot Jun 29, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

To improve clarity and adhere to the writing principles, we should avoid unnecessary filler words like 'basically' and 'generally'.

Suggested change
The data format mapping in the TiCDC Debezium message basically follows the [Debezium data type mapping rules](https://debezium.io/documentation/reference/stable/connectors/mysql.html#mysql-data-types), which is generally consistent with the native message of the Debezium Connector for MySQL. However, for some data types, the following differences exist between TiCDC Debezium and Debezium Connector messages:
The data format mapping in the TiCDC Debezium message follows the [Debezium data type mapping rules](https://debezium.io/documentation/reference/stable/connectors/mysql.html#mysql-data-types), which is consistent with the native message of the Debezium Connector for MySQL. However, for some data types, the following differences exist between TiCDC Debezium and Debezium Connector messages:
References
  1. Avoid unnecessary words and repetition. (link)


- Currently, TiDB does not support spatial data types, including GEOMETRY, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, and GEOMETRYCOLLECTION.

Expand Down