Skip to content

branch-2.1: [fix](mtmv)The refresh method for MTMV is commit. If the status is PAUSED, no more tasks should be generated #46020 #46265

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
Merged
yiguolei merged 1 commit into from
Jan 2, 2025
Merged

branch-2.1: [fix](mtmv)The refresh method for MTMV is commit. If the status is PAUSED, no more tasks should be generated #46020 #46265

yiguolei merged 1 commit into from
Jan 2, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jan 2, 2025

Cherry-picked from #46020

@zddr
[fix](mtmv)The refresh method for MTMV is commit. If the status is PA…
38fa15a 
…USED, no more tasks should be generated (#46020)

### What problem does this PR solve?
The refresh method for MTMV is commit. If the status is PAUSED, no more
tasks should be generated

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:
The refresh method for MTMV is commit. If the status is PAUSED, no more
tasks should be generated
@hello-stephen
Copy link
Contributor

hello-stephen commented Jan 2, 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 closed this Jan 2, 2025
@dataroaring dataroaring reopened this Jan 2, 2025
@hello-stephen
Copy link
Contributor

hello-stephen commented Jan 2, 2025

run buildall

@yiguolei yiguolei merged commit b5beaf4 into branch-2.1 Jan 2, 2025
18 of 19 checks passed
@github-actions github-actions bot deleted the auto-pick-46020-branch-2.1 branch January 2, 2025 06:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@hello-stephen @yiguolei @dataroaring @zddr