Aias00 opened a new issue, #973: URL: https://github.com/apache/rocketmq-dashboard/issues/973
## Problem\nRocketMQ Studio mounts under MySQL's init directory in . Those scripts run only while a data directory is first initialized. Existing volumes therefore never receive tables added by later Studio releases.\n\nThe current server now accesses persisted audit, K8s certificate, alert rule, and system alert tables. An existing deployment upgraded to this revision can fail with missing-table errors even though a fresh deployment succeeds. The repository contains , but docker-compose does not run it.\n\n## Evidence\n- : schema is mounted only to .\n- : an incremental migration exists but is not invoked.\n- : defines the newer tables.\n\n## Expected behavior\nUpgrades from a previously initialized MySQL volume apply all required schema changes deterministically.\n\n## Proposed fix\nAdd a versioned migration mechanism or an explicit startup upgrade step, and document the upgrade path. Include a regression test or compose-level verification for an existing database volume.\n\n# # Scope\nStudio persistence and deployment reliability. -- 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]
