[BugFix] MaxBy/MinBy not filter nulls (backport #51354)

[mergify]

Why I'm doing:

max_by/min_by should not filter nulls, for an example:

1. prepare data

create table test_table (
   `id` int NOT NULL,
   `name` varchar(10) DEFAULT NULL,
   `grade` int NOT NULL
) ENGINE=OLAP
PRIMARY KEY(`id`)
DISTRIBUTED BY HASH(`id`);

insert into test_table values (1,'john',90);
insert into test_table values (2,'jim',95);
insert into test_table values (3,NULL,100);

2. query Expected outcome 'null' actual outcome 'jim'

select max_by(name, grade) from test_table;

What I'm doing:

1. max_by and min_by not filter nulls;
2. fix ancient bug: crash caused by window query like max_by(T, S) over window_def when S's type is not same to T's

Fixes #issue

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 3.3
  • 3.2
  • 3.1
  • 3.0
  • 2.5

---

This is an automatic backport of pull request #51354 done by [Mergify](https://mergify.com). ## Why I'm doing:

max_by/min_by should not filter nulls, for an example:

1. prepare data

create table test_table (
   `id` int NOT NULL,
   `name` varchar(10) DEFAULT NULL,
   `grade` int NOT NULL
) ENGINE=OLAP
PRIMARY KEY(`id`)
DISTRIBUTED BY HASH(`id`);

insert into test_table values (1,'john',90);
insert into test_table values (2,'jim',95);
insert into test_table values (3,NULL,100);

2. query Expected outcome 'null' actual outcome 'jim'

select max_by(name, grade) from test_table;

What I'm doing:

1. max_by and min_by not filter nulls;
2. fix ancient bug: crash caused by window query like max_by(T, S) over window_def when S's type is not same to T's

Fixes #issue

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

[mergify]

@mergify[bot]: Backport conflict, please reslove the conflict and resubmit the pr

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud