morningman opened a new pull request, #65942: URL: https://github.com/apache/doris/pull/65942
## What this PR does Two independent fixes for P0 regression failures on branch-4.0 (surfaced in internal CI build 203615). ### 1. `information_schema.routine_load_jobs` returns empty error columns on a non-master FE (product fix) `FIRST_ERROR_MSG` / `ERROR_LOG_URLS` of a routine load job are transient, in-memory fields maintained **only on the master FE** (set in `RoutineLoadJob.executeTaskOnTxnStatusChanged` on task-txn commit; the follower replay path never sets them). `information_schema.routine_load_jobs` is served by the local (coordinating) FE, so on a non-master FE these columns come back empty, while `SHOW ROUTINE LOAD` (forwarded to the master) shows them. In a multi-FE cluster the two views are inconsistent, which made `test_routine_load_first_error_msg` fail (~4/5 runs). **Fix:** route the `routine_load_jobs` scan to the master FE, the same way `information_schema.tables` is already routed, gated by the existing `enable_schema_scan_from_master_fe` session variable (default `true`). No BE change, no test change needed. ### 2. Flaky `ann_index_basic` — `sql_ip_asc` empty result (test fix) Queries whose top-n cannot be evaluated by the ANN index (Asc `inner_product`, Desc `l2`, small-predicate top-n) fall back to a brute-force scan. Right after an INSERT the freshly written raw rows can be briefly invisible to that scan, so the ordered query intermittently returns nothing. **Fix:** add a scan-visibility gate after each INSERT that waits until a real row read (`select id`, not `count(*)` which may take a metadata shortcut) returns the expected number of rows. `.out` and `qt_` tags are unchanged. ## Verification - FE change is minimal and type-checked; not built/e2e-locally — relying on PR CI. - Root causes confirmed by code path + CI history (routine_load 4/5 fail, ann_index ~2/20). 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
