zqr10159 commented on PR #4369: URL: https://github.com/apache/hertzbeat/pull/4369#issuecomment-5577206891
@Duansg Thanks for the update. I rechecked commit `6731e6b3c74facac0f5897365a361b873cb9b68f` against the official `1.8.0` source. The previous authorization wording and positional `INSERT ... SELECT *` concerns are addressed. One release-scope clarification remains in the linked general upgrade guide: - `home/docs/start/update-1.9.0.md:403` correctly states that released 1.8.x has no SOP schedules, so there are no historical schedules to restore when upgrading from that release. I also checked the `1.8.0` tree for the schedule implementation and `hzb_sop_schedule` references; neither is present. - However, `home/docs/start/upgrade.md:152–176` still includes **AI Schedule Ownership After Upgrade**, instructing operators to recover legacy schedules and edit conversation/schedule creator columns. The Chinese counterpart retains the same instructions at `home/i18n/zh-cn/docusaurus-plugin-content-docs/current/start/upgrade.md:131–151`. Those recovery instructions may describe development-snapshot data, but their applicability is not stated. They are not a required step for the released 1.8.0 → 1.9.0 path and could lead operators to attempt unnecessary manual database changes. Since this release guide deliberately excludes RC/development-snapshot compatibility, please remove that legacy schedule recovery section from both general upgrade pages, keeping the new guide's explanation of 1.9.0 ownership behavior. This is a documentation scope/consistency correction, not a new defect in the migration implementation. -- 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]
