yuluo-yx opened a new pull request, #4394: URL: https://github.com/apache/rocketmq-dashboard/pull/4394
<!-- Make sure the base branch is `master`: that is the RocketMQ Studio trunk. --> ### Which Issue(s) This PR Fixes - Fixes #3057 - Replaces #3058, closed by the branch switch in #4379. ### Brief Description This is a resubmission of #3058 against `master`, following the branch switch notice in #4379. The fork branch is unchanged; `master` is now the RocketMQ Studio trunk. Message Explorer 现在可在现有查询历史抽屉中保存、命名和复用查询条件。命名查询持久化到服务端，供不同浏览器和运维人员共享；应用只回填表单，点击「查询」才执行。 ## 改动说明 - 在原历史抽屉新增命名查询页签，保留消息与轨迹历史的原有回放行为。 - 支持 Topic 时间范围、Key、Message ID 条件的保存、搜索、应用、重命名和删除。 - 复用现有认证规则：读者可查看和应用，管理员可修改；按实例隔离，每实例最多 50 条。 - 通过实例行锁、当前锁定读和唯一约束处理并发保存、容量及重名；达到上限不会删除旧查询。 - 移除浏览器 localStorage 持久化；失败提示和刷新以服务端结果为准。 ## 升级与回滚 启动时执行幂等建表脚本，命名查询独立于执行历史保留策略。未合入版本中的个人本地预设不自动上传，需要保留的条件可重新命名保存。回滚应用提交即可，保留新增表及数据不会影响旧版本。详细说明见 `docs/zh/named-message-queries.md`。 Fixes #3057 ### How Did You Test This Change? ## 验证 - 相关前端测试：24 项通过。 - ESLint、TypeScript/Vite 生产构建、合并差异检查通过。 - 后端服务、CRUD 路由、幂等建表和并发容量测试，以及既有历史兼容测试通过。 - 已合入最新 `rocketmq-studio`，使用普通推送保留原提交历史。 - 未执行远端工作流、浏览器 E2E 或真实 Broker 测试。 验证日期：2026-09-14。 ### Checklist - [x] One coherent change; unrelated modifications are not bundled in - [x] Commit subject follows Conventional Commits (`feat:` / `fix:` / `refactor:` / `chore:` / `docs:` / `perf:`) - [x] Tests added or updated for non-trivial changes, test methods named `...Test` - [x] New UI text has both Chinese and English entries under `web/src/i18n/`, or the change does not add UI text - [x] Architecture constraints stay green (`mvn test` runs the ArchUnit checks), or the original verification scope is stated above - [x] New source files carry the ASF license header, or no new source files were added - [x] Documentation touched where behaviour changed (README / `docs/` / in-app help), or no documentation change was required -- 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]
