kunable2333 opened a new pull request, #54144:
URL: https://github.com/apache/doris/pull/54144

   
   ### What problem does this PR solve?
   When triggering a refresh mtmv task during schema change job, modify 
directly the mtmv status at the end of refresh mtmv, which resulted directly in 
the behavior of the materialized view being inconsistent with #49041 
   add check base table status before modifying the mtmv status at the end of 
the refresh mtmv task
   
   Issue Number: close #xxx
   
   Related PR: #49041 
   
   Problem Summary:
   before changing the mtmv status at the end of mtmv refresh, check if the 
base table status is SCHEMA_CHANGE
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test <!-- At least one of them must be included. -->
       - [ ] Regression test
       - [x] Unit Test
       - [ ] Manual test (add detailed scripts or steps below)
       - [ ] No need to test or manual test. Explain why:
           - [ ] This is a refactor/code format and no logic has been changed.
           - [ ] Previous test can cover this change.
           - [ ] No code files have been changed.
           - [ ] Other reason <!-- Add your reason?  -->
   
   - Behavior changed:
       - [ ] No.
       - [x] Yes. <!-- Explain the behavior change -->
    During the execution of the scheme change task, queries which related to 
the base table ,cannot be rewritten with related asynchronous materialized 
views.
   The previous logic was that after the refresh task was completed, the 
materialized view could be rewritten.
   - Does this need documentation?
       - [x] No.
       - [ ] Yes. <!-- Add document PR link here. eg: 
https://github.com/apache/doris-website/pull/1214 -->
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label <!-- Add branch pick label that this PR should 
merge into -->
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to