*: show backfill type in admin show ddl jobs

[tangenta]

What problem does this PR solve?

Issue Number: ref #35983

Problem Summary:

• There is no way to know whether a finished ADD INDEX statement used the "ingest" way to backfill the records.
• Support running multiple add index job with ingest way at the same time can cause the CPU usage being high. To reduce the effect to foreground workload, it is better to set a limit.

What is changed and how it works?

Before this PR:

+--------+-------------+------------+-----------+--------------+-----------+----------+-----------+---------------------+---------------------+---------------------+--------+
| JOB_ID | DB_NAME     | TABLE_NAME | JOB_TYPE  | SCHEMA_STATE | SCHEMA_ID | TABLE_ID | ROW_COUNT | CREATE_TIME         | START_TIME          | END_TIME            | STATE  |
+--------+-------------+------------+-----------+--------------+-----------+----------+-----------+---------------------+---------------------+---------------------+--------+
|    166 | addindexlit | t          | add index | public       |       158 |      160 |         3 | 2022-10-28 22:58:22 | 2022-10-28 22:58:22 | 2022-10-28 22:58:25 | synced |
|    165 | addindexlit | t          | add index | public       |       158 |      160 |         3 | 2022-10-28 22:58:21 | 2022-10-28 22:58:21 | 2022-10-28 22:58:22 | synced |
+--------+-------------+------------+-----------+--------------+-----------+----------+-----------+---------------------+---------------------+---------------------+--------+

After this PR:

+--------+-------------+------------+---------------------------+--------------+-----------+----------+-----------+---------------------+---------------------+---------------------+--------+
| JOB_ID | DB_NAME     | TABLE_NAME | JOB_TYPE                  | SCHEMA_STATE | SCHEMA_ID | TABLE_ID | ROW_COUNT | CREATE_TIME         | START_TIME          | END_TIME            | STATE  |
+--------+-------------+------------+---------------------------+--------------+-----------+----------+-----------+---------------------+---------------------+---------------------+--------+
|    166 | addindexlit | t          | add index /* ingest */    | public       |       158 |      160 |         3 | 2022-10-28 22:58:22 | 2022-10-28 22:58:22 | 2022-10-28 22:58:25 | synced |
|    165 | addindexlit | t          | add index /* txn-merge */ | public       |       158 |      160 |         3 | 2022-10-28 22:58:21 | 2022-10-28 22:58:21 | 2022-10-28 22:58:22 | synced |
+--------+-------------+------------+---------------------------+--------------+-----------+----------+-----------+---------------------+---------------------+---------------------+--------+

The concurrent limit is set to 1 as well.

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.

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Benjamin2037
• hawkingrei

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.

[Benjamin2037]

LGTM

[Benjamin2037]

Do we need store the ingest type persist into job table or history table?

[hawkingrei]

/run-build

[tangenta]

Do we need store the ingest type persist into job table or history table?

@Benjamin2037 The type has been persisted in job.ReorgMeta.ReorgTp : )

[tangenta]

/merge

[ti-chi-bot]

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

Commit hash: 284c272

[sre-bot]

TiDB MergeCI notify

🔴 Bad News! New failing [1] after this pr merged.
These new failed integration tests seem to be caused by the current PR, please try to fix these new failed integration tests, thanks!

CI Name	Result	Duration	Compare with Parent commit
idc-jenkins-ci-tidb/sqllogic-test-1	🟥	2 min 33 sec	New failing
idc-jenkins-ci-tidb/integration-ddl-test	✅ all 6 tests passed	30 min	Fixed
idc-jenkins-ci-tidb/integration-compatibility-test	✅ all 1 tests passed	4 min 24 sec	Fixed
idc-jenkins-ci/integration-cdc-test	🟢 all 38 tests passed	20 min	Existing passed
idc-jenkins-ci-tidb/tics-test	🟢 all 1 tests passed	10 min	Existing passed
idc-jenkins-ci-tidb/integration-common-test	🟢 all 17 tests passed	10 min	Existing passed
idc-jenkins-ci-tidb/common-test	🟢 all 11 tests passed	9 min 56 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-2	🟢 all 28 tests passed	6 min 4 sec	Existing passed
idc-jenkins-ci-tidb/mybatis-test	🟢 all 1 tests passed	2 min 55 sec	Existing passed
idc-jenkins-ci-tidb/plugin-test	🟢 build success, plugin test success	4min	Existing passed