Skip to content

branch-3.0: [enhance](mtmv)Only restrict MTMV to not allow concurrent insert overwrite execution #48673 #49964

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
dataroaring merged 1 commit into from
Apr 25, 2025
Merged

branch-3.0: [enhance](mtmv)Only restrict MTMV to not allow concurrent insert overwrite execution #48673 #49964

dataroaring merged 1 commit into from
Apr 25, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Apr 10, 2025

Cherry-picked from #48673

@zddr
[enhance](mtmv)Only restrict MTMV to not allow concurrent insert over…
22a9557 
…write execution (#48673)

### What problem does this PR solve?

Related PR: #40558

Problem Summary:

Previously, on #40558, concurrent
execution of `INSERT OVERWRITE` was restricted for all OLAP tables to
address potential issues caused by concurrent execution.

In this current PR, the restriction has been modified to only apply to
Materialized Views (MTMV), as it appears that users can tolerate the
uncertainty in execution results caused by concurrency for OLAP tables.


### Release note

Only restrict MTMV to not allow concurrent insert overwrite execution
@github-actions github-actions bot requested a review from dataroaring as a code owner April 10, 2025 09:44
@hello-stephen
Copy link
Contributor

hello-stephen commented Apr 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 Apr 10, 2025
@hello-stephen
Copy link
Contributor

hello-stephen commented Apr 10, 2025

run buildall

dataroaring
dataroaring approved these changes Apr 25, 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

@dataroaring dataroaring merged commit c5c1891 into branch-3.0 Apr 25, 2025
22 of 24 checks passed
@github-actions github-actions bot deleted the auto-pick-48673-branch-3.0 branch April 25, 2025 11:15
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

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@hello-stephen @dataroaring @zddr