Duansg commented on PR #4369: URL: https://github.com/apache/hertzbeat/pull/4369#issuecomment-5577859480
@zqr10159 Agreed, and confirmed against the 1.8.0 tree: `SopSchedule`, `hzb_sop_schedule` and `/api/ai/schedule` are all absent there — the feature landed after 1.8.0 in #4016 (d99b5dbff5). The recovery procedure had no applicable target on the released 1.8.x → 1.9.0 path. Removed `AI Schedule Ownership After Upgrade` from both `home/docs/start/upgrade.md` and its Chinese counterpart. No document linked to that anchor, so nothing breaks. The 1.9.0 ownership behaviour stays in `update-1.9.0.md`, together with the scope statement that an upgrade from 1.8.x produces no historical schedules to restore. I also checked the remaining `upgrade.md` sections against 1.8.0 for the same release-scope issue — SFTP host keys, the `/api/logs/**` routes, `hzb_logs`/`hzb_traces` and `hertzbeat_logs` all exist there, so no other section has this problem. -- 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]
