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 all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5fe3d90
Fix broken external documentation link
wenxiaojie1 Jun 29, 2026
db67743
Address documentation style feedback
wenxiaojie1 Jun 29, 2026
1225c39
Address documentation style feedback
wenxiaojie1 Jun 29, 2026
bb4807b
docs: update LangChain TiDBVectorStore reference
wenxiaojie1 Aug 7, 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/langchain-community/vectorstores/tidb_vector/TiDBVectorStore) in LangChain documentation.

## 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/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:

@coderabbitai coderabbitai Bot Aug 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

Clarify that the Debezium rules are the baseline, not an exact match.

The sentence says that TiCDC follows Debezium rules and is consistent with the native connector, but the following bullets list mapping differences. State the baseline and limit the consistency claim to avoid implying that all TiCDC values match native Debezium values.

Suggested change
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:
The TiCDC Debezium message uses the [Debezium data type mapping rules](https://debezium.io/documentation/reference/stable/connectors/mysql.html#mysql-data-types) as its baseline and is generally consistent with the native message of the Debezium Connector for MySQL. However, differences exist for some data types, as described below:

As per path instructions, provide a committable suggestion for a safe contiguous Markdown fix and preserve the existing terminology and link structure.

Source: Path instructions


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

Expand Down
Loading