You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "unbridled-41 (via GitHub)" <gi...@apache.org> on 2026/09/12 12:00:08 UTC
[I] [Studio][Feature] Edit topic configuration (queues, perm, remark) from the topic page [rocketmq-dashboard]
unbridled-41 opened a new issue, #4248:
URL: https://github.com/apache/rocketmq-dashboard/issues/4248
## 1. Requested feature and source
Let operators **edit a topic's configuration from the UI** — queue counts, permission and remark — instead of only creating and deleting topics.
Source: the parent classic dashboard ships this as the row action "Topic CONFIG" (`frontend-new/src/pages/Topic/topic.jsx:498-500`), which opens `TopicModifyDialog` in update mode (`frontend-new/src/components/topic/TopicModifyDialog.jsx`, `bIsUpdate`): name and type are disabled while write/read queue counts and perm stay editable, submitting through `createOrUpdateTopic` (`frontend-new/src/api/remoteApi/remoteApi.js:674`).
## 2. Use case and impact
Resizing queues and tightening permissions (RW → RO/WO) is routine topic lifecycle management in the classic dashboard. Studio's topic page offers detail / send / delete only, so these operations require CLI access today.
The gap is an omission, not a design decision:
- The server endpoint already exists and is fully implemented for **all three providers** (`TopicController.updateTopic` → `ApacheInstanceProvider` / `AliyunInstanceProvider` / `TencentInstanceProvider`).
- The project's own API reference documents it as a supported operation (`docs/api-spec.md` §5.4 `POST /api/topics/update`).
- The frontend service wrapper exists (`web/src/services/topicService.ts` `updateTopic`, with demo-mode support) but **no page calls it** — the Apache provider even carries a comment about preserving values "on partial updates (e.g. perm or remark only)", written for update callers that never arrived in the UI.
## 3. Why it matters
- Parity with the parent project's topic management.
- Unlocks the documented, backend-complete update API for UI users without new server code.
- Cloud instances benefit too: the Aliyun/Tencent providers implement remark(-only) updates, matching what those APIs support.
## 4. Expected behavior / acceptance criteria
1. Topic rows expose a config edit action that opens the existing create dialog in edit mode, prefilled with the row's saved values.
2. Following the classic dialog semantics, name and type are disabled in edit mode; write/read queue counts, perm and remark are editable for Apache instances. Cloud instances keep the create dialog's vendor gating (no queue/perm fields — remark-only update, matching the Aliyun/Tencent provider implementations).
3. Submitting calls `updateTopic` with the selected instance id, then reloads the server-paged list; the create flow keeps working exactly as before (a cancelled edit must not turn the next create into an update).
## 5. Related PR
Fix incoming.
--
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: commits-unsubscribe@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Studio][Feature] Edit topic configuration (queues, perm, remark) from the topic page [rocketmq-dashboard]
Posted by "RockteMQ-AI (via GitHub)" <gi...@apache.org>.
RockteMQ-AI commented on issue #4248:
URL: https://github.com/apache/rocketmq-dashboard/issues/4248#issuecomment-5645760418
Thank you for this feature request! 🚀
I've reviewed the proposal and this appears to be a valid enhancement request for the RocketMQ Dashboard.
**Classification:** Enhancement
**Component:** Studio / Dashboard UI
**Next Steps:**
- This feature request has been noted and will be reviewed by the maintainers
- If you'd like to contribute this feature, please feel free to submit a PR
- For complex features, consider discussing the design approach first in the issue comments
**Additional Context:**
- Related documentation: [RocketMQ Dashboard](https://github.com/apache/rocketmq-dashboard)
- Contribution guide: [How to contribute](http://rocketmq.apache.org/docs/how-to-contribute/)
---
<sub>🤖 Automated analysis by github-manager | Issue classification: enhancement</sub>
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Studio][Feature] Edit topic configuration (queues, perm, remark) from the topic page [rocketmq-dashboard]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #4248:
URL: https://github.com/apache/rocketmq-dashboard/issues/4248#issuecomment-5746358720
This issue has been automatically closed because there has been no activity for 7 days. If you believe this issue is still relevant, please reopen it with updated information.
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Studio][Feature] Edit topic configuration (queues, perm, remark) from the topic page [rocketmq-dashboard]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #4248: [Studio][Feature] Edit topic configuration (queues, perm, remark) from the topic page
URL: https://github.com/apache/rocketmq-dashboard/issues/4248
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org