infoschema: load auto id related changes for multi-schema-change diff | tidb-test=pr/2320

[D3Hunter]

What problem does this PR solve?

Issue Number: close #47899

Problem Summary:

What changed and how does it work?

Check List

Tests

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

for the case in the issue

mysql>  create table t (a int not null auto_increment primary key, b int) auto_id_cache 100;insert into t (b) values (1);
Query OK, 0 rows affected (0.09 sec)

Query OK, 1 row affected (0.01 sec)

mysql> select * from t;
+---+------+
| a | b    |
+---+------+
| 1 |    1 |
+---+------+
1 row in set (0.00 sec)

mysql> alter table t add column c int, auto_increment 200;
Query OK, 0 rows affected (0.31 sec)

mysql> insert into t (b) values (2);
Query OK, 1 row affected (0.01 sec)

mysql> select * from t;
+-----+------+------+
| a   | b    | c    |
+-----+------+------+
|   1 |    1 | NULL |
| 200 |    2 | NULL |
+-----+------+------+
2 rows in set (0.00 sec)

• 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

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

[tiprow]

Hi @D3Hunter. 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/test-infra repository.

[D3Hunter]

there's no insert before alter table, so it works

[codecov]

Codecov Report

Attention: Patch coverage is 90.69767% with 4 lines in your changes missing coverage. Please review.

Project coverage is 56.0237%. Comparing base (66ba419) to head (569d50a).
Report is 1328 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #52967         +/-   ##
=================================================
- Coverage   72.3850%   56.0237%   -16.3613%     
=================================================
  Files          1482       1614        +132     
  Lines        428662     607125     +178463     
=================================================
+ Hits         310287     340134      +29847     
- Misses        99083     243692     +144609     
- Partials      19292      23299       +4007     

Flag	Coverage Δ
integration	37.1406% <86.0465%> (?)
unit	70.9157% <74.4186%> (-0.3039%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	50.3689% <ø> (+9.2149%)	⬆️

[D3Hunter]

/retest

[tiprow]

@D3Hunter: 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/test-infra repository.

[purelind]

/check-issue-triage-complete

[zimulala]

Using SubTypes instead of ActionTypes? Thus unified with the Type field and MultiSchemaInfo.SubJobs. Just a suggestion

[D3Hunter]

/retest

[tiprow]

@D3Hunter: 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/test-infra repository.

[zimulala]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-04-30 02:50:23.9629025 +0000 UTC m=+325577.720038073: ☑️ agreed by tiancaiamao.
• 2024-04-30 06:27:52.037006158 +0000 UTC m=+338625.794141731: ☑️ agreed by zimulala.

[D3Hunter]

/retest

[tiprow]

@D3Hunter: 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/test-infra repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tangenta, tiancaiamao, zimulala

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 [tangenta,tiancaiamao,zimulala]
• pkg/ddl/OWNERS [tangenta,zimulala]
• pkg/infoschema/OWNERS [tangenta,zimulala]
• pkg/parser/OWNERS [tangenta]

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]

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

[ti-chi-bot]

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

[lance6716]

/cherry-pick release-6.5

[ti-chi-bot]

@lance6716: new pull request created to branch release-6.5: #53735.

In response to this:

/cherry-pick release-6.5

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 ti-community-infra/tichi repository.

[ti-chi-bot]

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