executor: fix unexpected NotNullFlag in case when expr ret type

[guo-shaoge]

Signed-off-by: guo-shaoge [email protected]

What problem does this PR solve?

Issue Number: close #23036

Problem Summary:

drop table if exists t1;
create table t1(c1 int not null);
insert into t1 values(1);
select (case when null then c1 end) is null from t1;

Output should be empty set, but TiDB output "1". Because when we fold constant for IsNull expr, optimizer found the result type of CaseWhen expr has NotNullFlag, which is unexpected. So rewriter return false directly

What is changed and how it works?

What's Changed:

1. Erase NotNullFlag from the result type of CaseWhen expr. Because we don't know will any when clause be true until runtime.
2. make types.setTypeFlag() public. (types.setTypeFlag() -> types.SetTypeFlag())

Related changes

• Need to cherry-pick to the release branch

Check List

Tests

• Integration test: Add cases in expression.TestBuiltin()

Side effects: no

Release note

• fix unexpected NotNullFlag in case when expr ret type

[guo-shaoge]

PTAL @lzmhhh123

[XuHuaiyu]

LGTM

[ti-chi-bot]

@XuHuaiyu: Please use /LGTM instead of LGTM when you want to approve the pull request by comment.
If you use the GitHub review feature, please approve the PR directly, the comment will not take effect in the GitHub review feature.
If you have any qustions please refer to lgtm command help or lgtm plugin design.

If you have approved this PR, please ignore this reply. This reply is being used as a temporary reply during the migration of the new bot and will be removed on April 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.

[qw4990]

/LGTM

[XuHuaiyu]

/LGTM

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• XuHuaiyu
• qw4990

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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[XuHuaiyu]

/merge

[ti-chi-bot]

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

/run-all-tests

You only need to trigger /merge once, and 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]

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

Commit hash: faadae1

[ti-srebot]

cherry pick to release-4.0 in PR #23135

[AilinKid]

/run-cherry-picker

[ti-srebot]

cherry pick to release-5.0-rc in PR #23340