tju-yxq opened a new issue, #2526: URL: https://github.com/apache/rocketmq-dashboard/issues/2526
The development demo SQL under `deploy/mysql/` still targets the schema that existed before the numeric-ID standardization. The clearest failure is `upgrade-demo-instance.sql`: it still alters and inserts into `rmq_topic` and `rmq_group`, while the current schema uses `rmq_instance_topic` and `rmq_instance_group`. Running the documented script after initializing the current schema fails with MySQL error 1146 (`Table 'rocketmq.rmq_topic' doesn't exist`). The related ACL and alert helpers also still describe `VARCHAR` primary keys and `created_at` / `updated_at` columns. Current entities and `schema.sql` use numeric auto-increment IDs plus `gmt_create` / `gmt_modified`. The ACL script currently relies on `INSERT IGNORE` coercing obsolete string IDs instead of following the actual contract, and the alert helper can create incompatible tables when they are missing. These files are linked from the deployment documentation, so the checked-in demo workflow should be executable against the checked-in schema. Proposed behavior: - treat the instance and ACL files as development-only data loaders, not schema migrations; - let MySQL allocate numeric IDs; - resolve topic and consumer-group `instance_id` values from the stable instance name; - use the current `rmq_instance_topic` and `rmq_instance_group` tables; - make repeated imports idempotent without overwriting operator-modified ACL credentials or rules; - make the alert compatibility helper create the same numeric/timestamp columns as `schema.sql`; - document the required import order and production warning; - add an automated contract test that initializes the canonical schema, imports the scripts twice, and checks counts and referential integrity. -- 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]
