[BugFix] Fix mv refresh with multi partition columns ref base tables (backport #52017)

[mergify]

Why I'm doing:

When partitions p4 and p5 in the base table t1 change, cascading will cause the refresh of p1 and p5 in the materialized view mv1. However, p1 includes two partitions, 2020-07-01 and 2020-07-02, and the partition 2020-07-02 does not only come from the partition p4. Therefore, other partitions it depends on must also be taken into account.

Since p1 contains two partitions, 2020-07-01 and 2020-07-02, and the partition 2020-07-02 is not solely derived from the p4 partition, other partitions it depends on must also be considered when cascading the refresh. Therefore, during the cascaded refresh, it is necessary to include partitions p1, p2, and p3 that have not changed:

What I'm doing:

• Fix mv refresh with multi partition columns ref base tables

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 #52017 done by [Mergify](https://mergify.com). ## Why I'm doing:

When partitions p4 and p5 in the base table t1 change, cascading will cause the refresh of p1 and p5 in the materialized view mv1. However, p1 includes two partitions, 2020-07-01 and 2020-07-02, and the partition 2020-07-02 does not only come from the partition p4. Therefore, other partitions it depends on must also be taken into account.

Since p1 contains two partitions, 2020-07-01 and 2020-07-02, and the partition 2020-07-02 is not solely derived from the p4 partition, other partitions it depends on must also be considered when cascading the refresh. Therefore, during the cascaded refresh, it is necessary to include partitions p1, p2, and p3 that have not changed:

What I'm doing:

• Fix mv refresh with multi partition columns ref base tables

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]

Cherry-pick of 3c896df has failed:

On branch mergify/bp/branch-3.3/pr-52017
Your branch is up to date with 'origin/branch-3.3'.

You are currently cherry-picking commit 3c896df731.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   fe/fe-core/src/main/java/com/starrocks/scheduler/mv/MVPCTRefreshListPartitioner.java
	modified:   fe/fe-core/src/main/java/com/starrocks/scheduler/mv/MVPCTRefreshPartitioner.java
	modified:   fe/fe-core/src/main/java/com/starrocks/scheduler/mv/MVPCTRefreshRangePartitioner.java
	modified:   fe/fe-core/src/main/java/com/starrocks/sql/common/PCell.java
	modified:   fe/fe-core/src/main/java/com/starrocks/sql/common/PListCell.java
	modified:   fe/fe-core/src/main/java/com/starrocks/sql/common/PRangeCell.java
	modified:   fe/fe-core/src/test/java/com/starrocks/scheduler/PCTRefreshListPartitionOlapTest.java
	modified:   test/test_sql_cases.py

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   fe/fe-core/src/main/java/com/starrocks/catalog/combinator/AggStateCombinator.java
	deleted by us:   fe/fe-core/src/main/java/com/starrocks/catalog/combinator/AggStateMergeCombinator.java
	deleted by us:   fe/fe-core/src/main/java/com/starrocks/catalog/combinator/AggStateUnionCombinator.java

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[mergify]

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

[sonarcloud]

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

[LiShuMing]

@mergify backport branch-3.3.5

[mergify]

backport branch-3.3.5

✅ Backports have been created

• #52042 [BugFix] Fix mv refresh with multi partition columns ref base tables (backport #52017) (backport #52033) has been created for branch branch-3.3.5