Fix the compatibility issue in func FunctionIPv4NumToString

[solotzg]

What problem does this PR solve?

Issue Number: close #8211
Problem Summary:

CREATE TABLE t0(c0 INT);
ALTER TABLE t0 SET TIFLASH REPLICA 1;
SELECT SLEEP(5);

SELECT /*+ READ_FROM_STORAGE(TIKV[t0])*/t0.c0 FROM t0 WHERE INET_NTOA(t0.c0);
SELECT /*+ READ_FROM_STORAGE(TIFLASH[t0])*/t0.c0 FROM t0 WHERE INET_NTOA(t0.c0); -- ERROR 1105 (HY000): other error for mpp stream: Code: 43, e.displayText() = DB::Exception: Illegal type Int32 of argument of function IPv4NumToString, expected UInt32, e.what() = DB::Exception,

FunctionIPv4NumToString only supports argument whose type is UInt32.

What is changed and how it works?

• Make FunctionIPv4NumToString support unsigned integer data type.
• MySQL will return NULL and warning if failed to cast into 4 bytes unsigned integer(include Out of range). Under MPP mode, TiFlash will omit warning.
  • Warning 1411: Incorrect integer value: '?.?.?' for function inet_ntoa

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

Fix the compatibility issue in expression `inet_ntoa()`

[solotzg]

/cc @windtalker

[yibin87]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-10-19 09:08:13.635393849 +0000 UTC m=+1907291.222503996: ☑️ agreed by windtalker.
• 2023-10-19 09:50:59.672997373 +0000 UTC m=+1909857.260107503: ☑️ agreed by yibin87.

[solotzg]

/approve

[ti-chi-bot]

@solotzg: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

• Currently the CI jobs are not prow job style, we need it to notify Jenkins server to run them.
• 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.

If you have any questions about the PR merge process, please refer to pr process.

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: guo-shaoge, solotzg, windtalker, yibin87

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 [guo-shaoge,solotzg,windtalker,yibin87]

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

[solotzg]

/run-integration-test

[solotzg]

/cherry-pick release-7.5

[ti-chi-bot]

@solotzg: new pull request created to branch release-7.5: #8226.

In response to this:

/cherry-pick release-7.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.

[solotzg]

/cherry-pick release-7.1

[solotzg]

/cherry-pick release-6.5

[ti-chi-bot]

@solotzg: new pull request created to branch release-7.1: #8227.

In response to this:

/cherry-pick release-7.1

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]

@solotzg: new pull request created to branch release-6.5: #8228.

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.