lightning: support null value for auto-incr column on local backend

[dsdashun]

What problem does this PR solve?

Issue Number: close #34208

Problem Summary:

What is changed and how it works?

When encoding the SQL into a TiDB KV for importing, if the value is NULL in a 'not-null' column, go on further processing on special column types rather than convert those NULL values into zero values directly

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:

• D3Hunter
• gozssky

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.

[sre-bot]

Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/b487c521d1e180726512b1971968b9babf9aad11

[dsdashun]

/cc @gozssky @D3Hunter PTAL

[ti-chi-bot]

@dsdashun: GitHub didn't allow me to request PR reviews from the following users: PTAL.

Note that only pingcap members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @gozssky @D3Hunter PTAL

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.

[sleepymole]

rest LGTM

[sleepymole]

/run-integration-br-test

[dsdashun]

/run-check_dev_2

[D3Hunter]

rest lgtm

[D3Hunter]

current behavior looks odd to me, in data file it's null for a auto_incrment primary key column, then we generate an id automatically for it. what if it's just an corrupted data file, in that case we should not do it:

what's current behavior for case below:

table is create table t(id int primary key auto_increment, v varchar(10));, but in data file(csv), we have:

1,aaa
NULL,bbb
NULL,ccc
2,ddd

[sleepymole]

@D3Hunter TiDB supports insert NULL as auto_incrment column.

mysql> create table t(id int primary key auto_increment, v varchar(10));
Query OK, 0 rows affected (0.12 sec)

mysql> insert into t values (1, 'aaa');
Query OK, 1 row affected (0.03 sec)

mysql> insert into t values (NULL, 'bbb');
Query OK, 1 row affected (0.02 sec)

mysql> insert into t values (NULL, 'ccc');
Query OK, 1 row affected (0.01 sec)

mysql> insert into t values (2, 'ddd');
ERROR 1062 (23000): Duplicate entry '2' for key 'PRIMARY'
mysql> select * from t;
+----+------+
| id | v    |
+----+------+
|  1 | aaa  |
|  2 | bbb  |
|  3 | ccc  |
+----+------+
3 rows in set (0.01 sec)

For local backend, we need to enable duplicate-resolution to detect the primary key conflict.

[dsdashun]

/run-integration-br-test

[sleepymole]

/merge

[ti-chi-bot]

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

Commit hash: f5efbc9

[ti-srebot]

cherry pick to release-6.0 in PR #34595

[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/integration-cdc-test	🟥 failed 1, success 33, total 34	31 min	New failing
idc-jenkins-ci-tidb/integration-common-test	🟢 all 11 tests passed	16 min	Existing passed
idc-jenkins-ci-tidb/common-test	🟢 all 12 tests passed	8 min 17 sec	Existing passed
idc-jenkins-ci-tidb/integration-ddl-test	🟢 all 6 tests passed	6 min 49 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-2	🟢 all 28 tests passed	5 min 49 sec	Existing passed
idc-jenkins-ci-tidb/tics-test	🟢 all 1 tests passed	5 min 42 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-1	🟢 all 26 tests passed	5 min 42 sec	Existing passed
idc-jenkins-ci-tidb/mybatis-test	🟢 all 1 tests passed	3 min 12 sec	Existing passed
idc-jenkins-ci-tidb/integration-compatibility-test	🟢 all 1 tests passed	3 min 1 sec	Existing passed
idc-jenkins-ci-tidb/plugin-test	🟢 build success, plugin test success	4min	Existing passed