restore: make incremental restore and log restore compatible

[3pointer]

What problem does this PR solve?

Issue Number: ref #54474

Problem Summary:

1. current incremental backup is not compatible with log backup in one restore command. this pr try to make them compatible.

What changed and how does it work?

1. skip cluster empty check when restore incremental + log backup.
2. provide an option for restore command to skip rewrite timestamp with a limitation ddl support.(NOTICE: this option will make incremental restore do a strict check for ddls by default)

Check List

Tests

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

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU

• Performance regression: Consumes more Memory

• Breaking backward compatibility
  In order to protect data not loss for later log restore, the new add option during incremental restore will perform a strict check for ddls by default. which means the restore could fail due to unsupported backfill ddl types appeared. such as Add Index/Modify Column/Reorg Partition.
  Documentation https://github.com/pingcap/docs-cn/pull/17893/files

• 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 the issue that allow log restore perform based on an incremental restore.

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tiprow]

Hi @3pointer. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[tangenta]

lgtm for ddl part

[codecov]

Codecov Report

Attention: Patch coverage is 53.33333% with 28 lines in your changes missing coverage. Please review.

Project coverage is 56.8557%. Comparing base (08147e7) to head (7942cd7).
Report is 28 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #54473         +/-   ##
=================================================
- Coverage   72.8476%   56.8557%   -15.9920%     
=================================================
  Files          1542       1670        +128     
  Lines        436136     614701     +178565     
=================================================
+ Hits         317715     349493      +31778     
- Misses        98837     241325     +142488     
- Partials      19584      23883       +4299     

Flag	Coverage Δ
integration	38.2798% <53.3333%> (?)
unit	71.8694% <10.0000%> (+0.0015%)	⬆️

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

Components	Coverage Δ
dumpling	52.9656% <ø> (ø)
parser	∅ <ø> (∅)
br	62.7210% <55.1724%> (+16.8368%)	⬆️

[BornChanger]

Suggested change

	// LogIncrementalCompat indicates whether this restore should enter a compatibility mode for incremental restore.
	// AllowPITRFromIncremental indicates whether this restore should enter a compatibility mode for incremental restore.

[3pointer]

/test pull-br-integration-test

[tiprow]

@3pointer: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

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-sigs/prow repository.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-07-05 09:54:55.62209269 +0000 UTC m=+5792.857326788: ☑️ agreed by tangenta.
• 2024-07-09 06:04:22.1897741 +0000 UTC m=+337559.425008213: ☑️ agreed by Leavrth.

[3pointer]

/hold for test passed

[3pointer]

/test check-dev2

[tiprow]

@3pointer: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test check-dev2

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.

[3pointer]

/test check-dev2

[tiprow]

@3pointer: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test check-dev2

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.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BornChanger, Leavrth, tangenta, YuJuncen

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:

• br/OWNERS [BornChanger,Leavrth,YuJuncen]
• pkg/ddl/OWNERS [tangenta]

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

[3pointer]

/unhold

[3pointer]

/retest

[tiprow]

@3pointer: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[BornChanger]

/retest

[tiprow]

@BornChanger: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.