Fix broken external documentation links

[wenxiaojie1]

Fixes #23161.

This updates the two external documentation links reported by the broken-link checker:

• Replaces the removed LangChain TiDB Vector sample page with the current TiDBVectorStore API reference.
• Replaces the Debezium MySQL 2.4 data-type mapping URL with the stable documentation URL.

Validation:

• Verified both replacement URLs return HTTP 200.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign breezewish for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

Welcome @wenxiaojie1!

It looks like this is your first PR to pingcap/docs 🎉.

I'm the bot to help you request reviewers, add labels and more, See available commands.

We want to make sure your contribution gets all the attention it needs!



Thank you, and welcome to pingcap/docs. 😃

[ti-chi-bot]

Hi @wenxiaojie1. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[pingcap-cla-assistant]

All committers have signed the CLA.

[gemini-code-assist]

Code Review

This pull request updates documentation links in the LangChain integration and TiCDC Debezium guides. The review feedback suggests minor improvements to align with the style guide, including enclosing the TiDBVectorStore class name in backticks and removing filler words like 'basically' and 'generally' for better clarity.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

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)

[gemini-code-assist]

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)