Skip to content

branch-3.0: [fix](schema-change) Fix sync MV loss due to index change #54285 - #54530

Closed
github-actions[bot] wants to merge 1 commit into
branch-3.0from
auto-pick-54285-branch-3.0
Closed

branch-3.0: [fix](schema-change) Fix sync MV loss due to index change #54285#54530
github-actions[bot] wants to merge 1 commit into
branch-3.0from
auto-pick-54285-branch-3.0

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Aug 10, 2025

Copy link
Copy Markdown
Contributor

Cherry-picked from #54285

@HastyshellYour Name
[fix](schema-change) Fix sync MV loss due to index change (#54285)
660a671
### What problem does this PR solve?
Problem Summary:
Creation of shadow index did not take define stmt and where clause of MV
into account, therefore, after index creation,
MV info will be lost.
This bug only affect index change on MV related columns. Other types of
heavy sc are not allowed on MV related columns.
@Thearas

Thearas commented Aug 10, 2025

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@Thearas

Thearas commented Aug 10, 2025

Copy link
Copy Markdown
Contributor

run buildall

dataroaring
dataroaring approved these changes Aug 12, 2025
View reviewed changes

@dataroaringdataroaring left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@github-actionsgithub-actionsBot added the approved Indicates a PR has been approved by one committer. label Aug 12, 2025
@github-actions

github-actionsBot commented Aug 12, 2025

Copy link
Copy Markdown
ContributorAuthor

PR approved by at least one committer and no changes requested.

@github-actions

github-actionsBot commented Aug 12, 2025

Copy link
Copy Markdown
ContributorAuthor

PR approved by anyone and no changes requested.

@gavinchou

gavinchou commented Aug 28, 2025

Copy link
Copy Markdown
Contributor

run buildall

@github-actions

github-actionsBot commented Feb 25, 2026

Copy link
Copy Markdown
ContributorAuthor

We're closing this PR because it hasn't been updated in a while.
This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable.
If you'd like to revive this PR, please reopen it and feel free a maintainer to remove the Stale tag!

@morningman
morningman deleted the auto-pick-54285-branch-3.0 branch July 8, 2026 14:32
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dataroaringdataroaringdataroaring approved these changes

Assignees

No one assigned

Labels

approvedIndicates a PR has been approved by one committer.reviewedStale

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@Thearas@gavinchou@dataroaring@Hastyshell