[Refactor] Remove IVM FULL refresh mode (backport #72288)

[mergify]

Why I'm doing:

What I'm doing:

user-visible refresh modes are limited to INCREMENTAL and PCT; FULL is removed. FULL has not been released, so no compatibility shim is needed.

• Drop FULL from MaterializedView.RefreshMode enum and isFull() helper
• Drop the FULL branch from MVRefreshProcessorFactory.newProcessor
• Reword the IVM schema-change error to "drop and re-create the MV" since the legacy "trigger a full refresh" path no longer exists
• Update affected unit tests and remove the iceberg_full SQL test
• Drop the FULL bullet from CREATE MATERIALIZED VIEW docs (en/zh/ja)

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 pr needs auto generate documentation
• 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
  • 4.1
  • 4.0
  • 3.5
  • 3.4

---

This is an automatic backport of pull request #72288 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 0056da9 has failed:

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

You are currently cherry-picking commit 0056da9f39.
  (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:   docs/en/sql-reference/sql-statements/materialized_view/CREATE_MATERIALIZED_VIEW.md
	modified:   docs/ja/sql-reference/sql-statements/materialized_view/CREATE_MATERIALIZED_VIEW.md
	modified:   docs/zh/sql-reference/sql-statements/materialized_view/CREATE_MATERIALIZED_VIEW.md
	modified:   fe/fe-core/src/main/java/com/starrocks/catalog/MaterializedView.java
	modified:   fe/fe-core/src/main/java/com/starrocks/scheduler/mv/BaseMVRefreshProcessor.java
	modified:   fe/fe-core/src/test/java/com/starrocks/alter/AlterMVJobExecutorEditLogTest.java
	modified:   fe/fe-core/src/test/java/com/starrocks/alter/AlterMaterializedViewTest.java
	modified:   fe/fe-core/src/test/java/com/starrocks/scheduler/mv/ivm/IVMBasedMvRefreshProcessorIcebergTest.java
	deleted:    test/sql/test_materialized_view_ivm/R/test_ivm_with_iceberg_full
	deleted:    test/sql/test_materialized_view_ivm/T/test_ivm_with_iceberg_full

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   fe/fe-core/src/main/java/com/starrocks/scheduler/mv/MVRefreshProcessorFactory.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

[Youngwb]

@mergify rebase

[mergify]

rebase

❌ Base branch update has failed

Details

PullRequest::RebaseConflictError

[Youngwb]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Resolved. The cherry-pick had unresolved conflict markers in MVRefreshProcessorFactory.java. Fixed in commit 16aa96d by removing the markers and using the renamed processor class names (MVHybridRefreshProcessor, MVIVMRefreshProcessor, MVPCTRefreshProcessor) consistent with the rename commit already in branch-4.1.

[github-actions]

🌎 Translation Required?

✅ All translation files are up to date.
Great job! No translation actions are required for this PR.

🕒 Last updated: Wed, 29 Apr 2026 08:35:32 GMT