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

   ### What problem does this PR solve?
   
   Issue Number: close #xxx
   
   Related PR: #37396
   
   Problem Summary:
   
   `test_create_mv_and_mtmv` verifies that an async MTMV can read a sync rollup 
MV, resolve the rollup column back to the base-table partition column, and 
complete full and partial refreshes.
   
   The original case disabled cost-based sync MV selection so both the 
precondition query and MTMV definition actually read the sync rollup. After 
that control was removed, `TRY_IN_RBO` could successfully generate the rollup 
candidate while cost-based planning still selected the base index, causing an 
intermittent `MaterializedViewRewriteSuccessButNotChose` failure before MTMV 
creation.
   
   Add `USE_MV` to both queries so the case deterministically exercises the 
intended sync-rollup path while retaining the existing full and partial refresh 
assertions.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test
       - [ ] Regression test
       - [ ] Unit Test
       - [x] Manual test (add detailed scripts or steps below)
           - Parsed the modified Groovy suite with `GroovyShell`.
           - Ran `git diff --check`.
       - [ ] 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.
           - [ ] Other reason
   
   - Behavior changed:
       - [x] No.
       - [ ] Yes.
   
   - Does this need documentation?
       - [x] No.
       - [ ] Yes.
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label
   


-- 
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