lightning: add a precheck for csv header

[glorv]

What problem does this PR solve?

Issue Number: close #27757

Problem Summary:

What is changed and how it works?

Verify if source csv files actually contain header line but the config is false

Proposal: xxx

What's Changed:

How it Works:
Try to find a table that satisfy following two restrict:

• contains at least 1 csv file(2 is prefered)
• contains a primary key or unique key

If the field values in the source files' first line match the table column names:

• if there are two source files and the table contains pk/uk, or the value of the fields are not compatible with the table column tables, then precheck report a critical erorr
• otherwise, report a warning.

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

Add a precheck for CSV header setting

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• gozssky
• kennytm

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.

[glorv]

/cc @kennytm

[kennytm]

rest LGTM

[kennytm]

🤔 it should copy the SQL mode from the config, not always using strict_trans_tables, because this affects the CastValue function below

[glorv]

The ModeStrictTransTables is by design. the SQL mode in config is likely to be a looser one (like the current default SQL mode of lightning), then failed type cast will be omited. And when the check logic reaches here, it means the values is the same as the row columns names (likely to be strings in the common case), so the possibility of meeting a false positive case (like a field name is 0000-00-00?🤔) is quite low.

[glorv]

/merge

[ti-chi-bot]

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

Commit hash: 02b3771

[ti-chi-bot]

@glorv: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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.