unbridled-41 opened a new issue, #5994: URL: https://github.com/apache/rocketmq-dashboard/issues/5994
### Studio Version branch: `rocketmq-studio` @ `7e7aa344` ### Runtime Environment Backend tests: `cd server && mvn -o -B -ntp test -Dtest='QueryHistorySchemaIndexTest'`. ### Describe the Bug `db/schema.sql` widens `rmq_instance_message.queried_by`, `rmq_instance_trace.queried_by` and `rmq_operation_audit.operator` to VARCHAR(128), but that file only runs on a new MySQL data directory (the deploy init script is mounted at `docker-entrypoint-initdb.d`) or in the dev H2 profile; an existing database never re-runs it, and no ApplicationRunner widened these columns. A volume initialised before the widening keeps VARCHAR(64). Since `AuthService` allows usernames up to 128 characters, such an account can log in while its query history and audit rows cannot be stored: on strict MySQL the insert fails and both writers only log at WARN (silently missing history/audit), on a laxer server the value is truncated and every owner-scoped read misses the row. ### Steps to Reproduce Create the two tables with `queried_by VARCHAR(64)`, start the application, then run a message query as a 100-character user. ### What Did You Expect to See? The history and audit rows stored. ### What Did You See Instead? They are dropped (strict mode) or stored under a truncated owner. ### Evidence `schema.sql` lines: "Existing deployments are upgraded by the application schema-migration runners after the application connects" - but no runner touches these columns (`grep -rn "MODIFY" server/src/main/java` finds none). ### Acceptance Criteria An existing database is widened at startup, idempotently and without failing the boot when the widening is refused, with a regression test. **Corresponding PR:** #ISSUEPR# -- 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]
