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

   ### What problem does this PR solve?
   
   During Gson deserialization, the no-arg constructor of MTMVStatus is 
invoked, which sets refreshState to "init". However, the 
org.apache.doris.mtmv.MTMVStatus#updateNotNull method determines which 
properties to modify by checking whether each parameter is null. The unintended 
side effect is that refreshState, which should remain null, gets initialized as 
"init", leading to unexpected behavior
   
   Issue Number: close #xxx
   
   Related PR: #xxx
   
   Problem Summary:
   Fix issue that refreshState turns to init when replaying alterStatus editLog 
   ### Release note
   
   Fix issue that refreshState turns to init when replaying alterStatus editLog 
   
   ### Check List (For Author)
   
   - Test <!-- At least one of them must be included. -->
       - [ ] Regression test
       - [ ] 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.
       - [ ] Yes. <!-- Explain the behavior change -->
   
   - Does this need documentation?
       - [ ] 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