yujun777 opened a new pull request, #68469:
URL: https://github.com/apache/doris/pull/68469
### What problem does this PR solve?
Issue Number: N/A
Related PR: N/A
Problem Summary: `SHOW ANALYZE TASK STATUS <id>` on a non-existent analyze
job id dereferenced the null `AnalysisInfo` returned by
`AnalysisManager.findJobInfo` without a null check, surfacing an internal
`NullPointerException` (`Cannot read field "catalogId" because "jobInfo" is
null`). It now reports `Analyze job [<id>] not exists`, consistent with the
existing error of `DROP ANALYZE JOB`. The regression case
`test_show_analyze_task_status_cmd` is extended with a `test{sql,exception}`
case for a missing job id.
### Release note
`SHOW ANALYZE TASK STATUS` with a non-existent analyze job id now returns a
clear "Analyze job [...] not exists" error instead of an internal
NullPointerException.
### Check List (For Author)
- Test:
- Regression test (`query_p0/show/test_show_analyze_task_status_cmd`,
extended with the not-exists case)
- Behavior changed: Yes. Only the error path for a non-existent analyze job
id changes: internal NullPointerException -> user-visible "Analyze job not
exists" error. Existing behavior for valid job ids is unchanged.
- Does this need documentation: No
--
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]
