*: fix bug that table name in 'admin show ddl jobs' is missing for ongoing drop table operation

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #42268

Problem Summary:

What is changed and how it works?

During drop table, the table is removed from the infoschema
So getTableName found nothing.
This cause the missing of the table name in 'admin show ddl jobs' result.

On the master branch, we can get the table name by job.TableName.
For older tidb, there is no TableName field, we need some other way to fix it.

Check List

Tests

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

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

Fix a bug that table name in 'admin show ddl jobs' is missing for ongoing drop table operation

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Defined2014
• bb7133

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[bb7133]

LGTM

[bb7133]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 7b52744

[tiancaiamao]

/merge

[tiancaiamao]

/run-unit-test

[tiancaiamao]

/test unit-test

[tiancaiamao]

/test unit-test

[hawkingrei]

/retest

[tiancaiamao]

/retest

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.1: #42945.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-5.4: #42946.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.0: #42947.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.2: #42948.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.3: #42949.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.4: #42950.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #42951.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.0: #42952.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-5.3: #42953.

[ti-chi-bot]

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

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/unit-test	7b52744	link	true	/test unit-test

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