[BugFix] Ignore to refresh if base table has dropped one partition (backport #52740)

mergify[bot] commented 1 week ago

Why I'm doing:

If base table's partition has dropped, it will trigger the whole partitions of mv to refresh.

What I'm doing:

Ignore to trigger mv refresh if the base table's partitions has been dropped.
MV refresh will be triggered only if this partition is recreated again.

Fixes https://github.com/StarRocks/starrocks/issues/52576

What type of PR is this:

[x] 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.
[x] 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:

[x] 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
[x] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch
- [x] 3.3
- [x] 3.2
- [ ] 3.1
- [ ] 3.0
- [ ] 2.5
  This is an automatic backport of pull request #52740 done by Mergify.
  Why I'm doing:
If base table's partition has dropped, it will trigger the whole partitions of mv to refresh.

What I'm doing:

Ignore to trigger mv refresh if the base table's partitions has been dropped.
MV refresh will be triggered only if this partition is recreated again.

Fixes https://github.com/StarRocks/starrocks/issues/52576

What type of PR is this:

[x] 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.
[x] 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:

[x] 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
[x] This is a backport pr

mergify[bot] commented 1 week ago

Cherry-pick of 5b50628507b4fbcf18b86e59c6f23fc8e8c8e02c has failed:

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

You are currently cherry-picking commit 5b50628507.
  (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)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
    both modified:   fe/fe-core/src/main/java/com/starrocks/connector/partitiontraits/DefaultTraits.java
    both modified:   fe/fe-core/src/main/java/com/starrocks/connector/partitiontraits/OlapPartitionTraits.java
    both modified:   fe/fe-core/src/test/java/com/starrocks/scheduler/PartitionBasedMvRefreshProcessorHiveTest.java

no changes added to commit (use "git add" and/or "git commit -a")

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[bot] commented 1 week ago

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