Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: branch-3.0
Choose a base branch
from
Open

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

wants to merge 1 commit into from
+83 −2

Conversation

github-actions[bot]
Copy link
Contributor

Cherry-picked from #54285

@TangSiyang2001
[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.
@github-actions github-actions bot requested a review from dataroaring as a code owner August 10, 2025 14:43
@Thearas
Copy link
Contributor

Thearas commented Aug 10, 2025

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?

@dataroaring dataroaring reopened this Aug 10, 2025
@Thearas
Copy link
Contributor

Thearas commented Aug 10, 2025

run buildall

dataroaring
dataroaring approved these changes Aug 12, 2025
View reviewed changes
Copy link
Contributor

@dataroaring dataroaring left a comment

Choose a reason for hiding this comment

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

LGTM

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Aug 12, 2025
@github-actions GitHub Actions
Copy link
Contributor Author

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

@github-actions GitHub Actions
Copy link
Contributor Author

PR approved by anyone and no changes requested.

@gavinchou
Copy link
Contributor

run buildall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dataroaring dataroaring dataroaring approved these changes

Assignees
No one assigned
Labels
approved Indicates a PR has been approved by one committer. reviewed
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@Thearas @gavinchou @dataroaring @TangSiyang2001