executor: fix ifnull bug when arg is enum/set

[guo-shaoge]

Signed-off-by: guo-shaoge shaoge1994@163.com

What problem does this PR solve?

Issue Number: close #24944

Problem Summary: Just as this comment said. ifnull will be removed if its first argument has not null attributes. But it doesn't work properly if first argument is enum/set. Because enum/set has two semantics(int/string). We may use its string semantics unexpectedly. So we cannot remote ifnull if its first argument is enum/set.

What is changed and how it works?

What's Changed: If ifnull's first argument is enum/set, doesn't rewrite it.

Related changes

• Need to cherry-pick to the release branch

Check List

Tests

• Integration test

Side effects: We may lose some performance for ifnull expression when argument is enum/set. But we have to do it to make it right.

Release note

• executor: fix ifnull bug when arg is enum/set

[guo-shaoge]

/cc @wshwsh12

[XuHuaiyu]

lgtm

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• XuHuaiyu
• lzmhhh123

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.

[lzmhhh123]

/merge

[ti-chi-bot]

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

Commit hash: 6697d5e

[ti-srebot]

cherry pick to release-5.0 in PR #25116

[lzmhhh123]

/run-cherry-picker

[ti-srebot]

cherry pick to release-4.0 in PR #26035