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

   ### What problem does this PR solve?
   
   Problem Summary:
   
   A successful `INSERT INTO dst SELECT ... FROM src` can repeatedly emit 
`ProgressManager` missing-meta warnings. Materialized view refreshes use the 
same INSERT execution path and can produce large volumes of these warnings.
   
   INSERT jobs have a load job ID but do not register scan progress. Reports 
may also arrive after a bulk load removes its progress entry. A missing entry 
therefore does not indicate an error. Remove the diagnostic entirely and 
continue updating only registered entries, consistent with `addTotalScanNums`. 
Backend statistics reporting and progress registration/cleanup remain unchanged.
   
   ### Release note
   
   Remove misleading missing-progress warnings for INSERT operations, including 
materialized view refreshes, and late load reports.
   
   ### Check List (For Author)
   
   - Test:
       - [x] Unit Test: `ProgressManagerTest` covers unregistered and removed 
entries without WARN/DEBUG messages, per-query/fragment accounting, completion, 
and retry reset.
       - [x] Manual test: reproduced the warning with a successful local INSERT 
SELECT; verified successful INSERT SELECT without new warnings after the 
initial logging fix.
       - FE build passed before the final diagnostic removal; final incremental 
source/test compilation and Checkstyle validation passed.
   - Behavior changed:
       - [x] Yes. Missing scan-progress entries no longer generate log messages.
   - Does this need documentation?
       - [x] No.
   
   ### 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