[DNM] hack pd client to support basic keyspace

[3AceShowHand]

What problem does this PR solve?

Issue Number: close #xxx

What is changed and how it works?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Questions

Will it cause performance regression or break compatibility?

Do you need to update user documentation, design documentation or monitoring documentation?

Release note

Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

[gemini-code-assist]

Summary of Changes

Hello @3AceShowHand, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a minor but important defensive programming change to the DDL history update logic. It adds a nil check to prevent potential runtime panics that could occur if database information is unexpectedly missing during schema DDL processing. This improves the overall stability of the system's DDL handling. The title "[DNM] hack pd client to support basic keyspace" appears to be a placeholder or refers to a broader, uncommitted scope, as the current change is focused solely on DDL history robustness.

Highlights

• Robustness Improvement: Implemented a nil check within updateDDLHistoryForSchemaDDL to prevent potential panics when accessing databaseInfo, ensuring safer handling of DDL events.
• DDL History Update Logic: Enhanced the DDL history update mechanism for schema DDLs by explicitly checking for the existence of database information before processing associated tables.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a nil-check in updateDDLHistoryForSchemaDDL to prevent a potential panic when the database information is not found. While this is a good defensive measure, the current implementation of returning nil could lead to incorrect DDL history tracking. My review includes a suggestion to align the behavior with other similar functions and ensure the DDL history is correctly updated.

[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 3aceshowhand 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.

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

[tenfyzhong]

Is this code for a quick test? Should I pick to my branch ?

[3AceShowHand]

for test, no need to pick.

[ti-chi-bot]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-linked-issue label, please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456.

_{📖 For more info, you can check the "Contribute Code" section in the development guide.}

[ti-chi-bot]

@3AceShowHand: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-error-log-review	c5b9a10	link	true	/test pull-error-log-review
pull-unit-test	c5b9a10	link	true	/test pull-unit-test
pull-cdc-kafka-integration-light	c5b9a10	link	true	/test pull-cdc-kafka-integration-light
pull-cdc-mysql-integration-light	c5b9a10	link	true	/test pull-cdc-mysql-integration-light
pull-cdc-pulsar-integration-light	c5b9a10	link	false	/test pull-cdc-pulsar-integration-light
pull-cdc-mysql-integration-heavy	c5b9a10	link	true	/test pull-cdc-mysql-integration-heavy
pull-cdc-storage-integration-heavy	c5b9a10	link	true	/test pull-cdc-storage-integration-heavy
pull-cdc-kafka-integration-heavy	c5b9a10	link	true	/test pull-cdc-kafka-integration-heavy
pull-cdc-storage-integration-light	c5b9a10	link	true	/test pull-cdc-storage-integration-light

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.