ddl, tables: support the column type change between the integer types

[zimulala]

What problem does this PR solve?

Issue Number: close #19118
Support the column type change between the integer types(no rollback operation is supported yet).

Related PR: pingcap/parser#966

What is changed and how it works?

Proposal: #18435

Related changes

• PR to update pingcap/docs/pingcap/docs-cn:
• Need to cherry-pick to the release branch

Check List

Tests

• Unit test

Release note

[codecov]

Codecov Report

Merging #19059 into master will increase coverage by 0.5462%.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             master     #19059        +/-   ##
================================================
+ Coverage   79.0884%   79.6347%   +0.5462%     
================================================
  Files           549        549                
  Lines        149047     152068      +3021     
================================================
+ Hits         117879     121099      +3220     
+ Misses        21659      21514       -145     
+ Partials       9509       9455        -54     

[zimulala]

PTAL @AilinKid @bb7133 @tangenta

[AilinKid]

LGTM

[zimulala]

PTAL @bb7133 @tangenta

[bb7133]

/run-unit-test

[AilinKid]

/run-check_dev_2

[AilinKid]

/run-unit-test

[AilinKid]

The CI failure analysis:

1: problem occurs with ctx.(sqlexec.RestrictedSQLExecutor).ExecRestrictedSQL(valStr), the session doesn't set its connectID to keep the database used. Here better change the table name in valStr to test.tt

2: better put modification of the job and tableInfo after the fail point.

failpoint.Inject("mockInsertValueAfterCheckNull", func(val failpoint.Value) {
....
}
updateChangingInfo(job, changingCol, changingIdxs, model.StateDeleteOnly)
job.Args = append(job.Args, changingCol, changingIdxs)

ver, err = updateVersionAndTableInfoWithCheck(t, job, tblInfo, originalState != changingCol.State)

Because once it errors in fail point, it will return without updateVersionAndTableInfoWithCheck. That will also cause the job updated with raw args which has already had the changingCol and ChangingIdxs appended.

[zimulala]

2: better put modification of the job and tableInfo after the fail point.

failpoint.Inject("mockInsertValueAfterCheckNull", func(val failpoint.Value) {
....
}
updateChangingInfo(job, changingCol, changingIdxs, model.StateDeleteOnly)
job.Args = append(job.Args, changingCol, changingIdxs)

ver, err = updateVersionAndTableInfoWithCheck(t, job, tblInfo, originalState != changingCol.State)

Because once it errors in fail point, it will return without updateVersionAndTableInfoWithCheck. That will also cause the job updated with raw args which has already had the changingCol and ChangingIdxs appended.

The failpoint is used for the test, so I think we needn't to do it. However, in order to get the test failure information more easily, I set the job state to JobStateCancelled.

[zimulala]

PTAL @bb7133 @tangenta

[zimulala]

/run-all-tests

[bb7133]

LGTM

[ti-srebot]

/run-all-tests

[ti-srebot]

@zimulala merge failed.