[BugFix] fix analyzing error in prepare stmt with HAVING clause

[ShaoxunLi]

Why I'm doing:

The following prepare statement fails to be executed :

starrocks> show variables like 'sql_mode';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| sql_mode      |       |
+---------------+-------+
1 row in set (0.00 sec)

starrocks> prepare stmt1 from select a from t group by a having count(*) = ?;
ERROR 1064 (HY000): Getting analyzing error. Detail message: ? must appear in the GROUP BY clause or be used in an aggregate function.

starrocks> prepare pp from select a, b from t group by a, b having a > ?;
ERROR 1064 (HY000): Getting analyzing error. Detail message: ? must appear in the GROUP BY clause or be used in an aggregate function.

What I'm doing:

the aggregation type will not be verified when the expression is a parameter,

starrocks> prepare stmt1 from select a from t group by a having count(*) = ?;
Query OK, 0 rows affected (0.00 sec)

starrocks> set @p1 = 1;
Query OK, 0 rows affected (0.01 sec)

starrocks> execute stmt1 using @p1 ;
+------+
| a    |
+------+
|    2 |
|    1 |
+------+
2 rows in set (0.02 sec)

starrocks> prepare pp from select a from t group by a having a > ?;
Query OK, 0 rows affected (0.00 sec)

starrocks> set @p1 = 1;
Query OK, 0 rows affected (0.01 sec)

starrocks> execute pp using @p1;
+------+
| a    |
+------+
|    2 |
+------+
1 row in set (0.03 sec)

Fixes #50584

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

[sonarcloud]

Quality Gate passed

Issues
4 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

[github-actions]

[Java-Extensions Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[BE Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[FE Incremental Coverage Report]

✅ pass : 2 / 2 (100.00%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	com/starrocks/sql/analyzer/AggregationAnalyzer.java	2	2	100.00%	[]

[ShaoxunLi]

@Seaven @wyb Can you review this PR? Thank you.

[github-actions]

@Mergifyio backport branch-3.3

[mergify]

backport branch-3.3

✅ Backports have been created

• #51258 [BugFix] fix analyzing error in prepare stmt with HAVING clause (backport #50583) has been created for branch branch-3.3