Lightning: Update Parameter Name from tikv-importer.incremental-import to tikv-importer.parallel-import

[lyzx2001]

What problem does this PR solve?

Issue Number: close #45501

Problem Summary:

The actual meaning of tikv-importer.incremental-import is to use the physical import mode for parallel import, which requires the target table to be empty. However, the current name may mislead users into thinking it is for incremental import, leading to misuse.
When the user misuses it and sets the duplicate-resolution to remove, conflicts between data in the source file and the existing data in the target table can lead to the mistaken deletion of the conflicting records in the target table.

What is changed and how it works?

1. Starting from version 7.3, the parameter name has been changed from tikv-importer.incremental-import to tikv-importer.parallel-import.
2. If users pass the parameter name as tikv-importer.incremental-import, it will be converted to tikv-importer.parallel-import for compatibility.

Since there exist multiple unit tests and integration tests that have covered test cases of tikv-importer.incremental-import, I changed some of them to tikv-importer.parallel-import, and let others remain as tikv-importer.incremental-import. If all of the related unit tests and integration tests can pass, that means the functionality of both tikv-importer.parallel-import and tikv-importer.incremental-import work 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.

Parameter name `tikv-importer.incremental-import` has been updated to `tikv-importer.parallel-import`. The meaning of this parameter is to use the physical import mode for parallel import, which requires the target table to be empty.

[lyzx2001]

/cc @lance6716

[codecov]

Codecov Report

Merging #45539 (37ea222) into master (2eb698c) will increase coverage by 0.6598%.
Report is 19 commits behind head on master.
The diff coverage is 60.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #45539        +/-   ##
================================================
+ Coverage   73.2247%   73.8845%   +0.6598%     
================================================
  Files          1265       1272         +7     
  Lines        389531     395842      +6311     
================================================
+ Hits         285233     292466      +7233     
+ Misses        86009      85195       -814     
+ Partials      18289      18181       -108     

Flag	Coverage Δ
integration	78.1388% <ø> (?)
unit	73.8772% <60.0000%> (+0.6525%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	54.0444% <ø> (ø)
parser	85.0554% <ø> (ø)
br	52.1743% <60.0000%> (+0.0544%)	⬆️

[lance6716]

/test pull-br-integration-test

[tiprow]

@lance6716: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test tiprow_fast_test

Use /test all to run all jobs.

In response to this:

/test pull-br-integration-test

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.

[lance6716]

/test pull-br-integration-test

[tiprow]

@lance6716: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test tiprow_fast_test

Use /test all to run all jobs.

In response to this:

/test pull-br-integration-test

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.

[lyzx2001]

/cc @D3Hunter

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, lance6716

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [D3Hunter,lance6716]

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]

[LGTM Timeline notifier]

Timeline:

• 2023-07-26 03:01:36.669357729 +0000 UTC m=+323439.263888705: ☑️ agreed by lance6716.
• 2023-07-26 06:24:42.14898032 +0000 UTC m=+335624.743511308: ☑️ agreed by D3Hunter.