RockteMQ-AI commented on issue #11443: URL: https://github.com/apache/rocketmq/issues/11443#issuecomment-6184848971
**Issue Evaluation** Category: `type/enhancement` | Status: **Evaluated** **Feasibility:** Feasible **Scope:** `tools/src/main/java/org/apache/rocketmq/tools/admin/` (mqadmin CLI layer) **Compatibility:** No breaking changes — additive CLI commands only **Assessment:** The request is well-researched. The broker-side batch deletion infrastructure already exists: - `AdminBrokerProcessor#deleteTopicList` / `#deleteSubscriptionGroupList` (RequestCodes 5002/5003) - `DeleteTopicListRequestBody` / `DeleteSubscriptionGroupListRequestBody` - Rate limiting via `BrokerConfig#batchDeleteTopicMaxRate` / `#batchDeleteSubscriptionGroupMaxRate` - Client-side API in `MQClientAPIImpl` The gap is purely at the mqadmin CLI level — adding `deleteTopicBatch` and `deleteSubGroupBatch` (or similar) commands that wrap the existing client calls. **Suggested implementation approach:** 1. Add new `SubCommand` implementations in the `tools` module (following the pattern of existing `DeleteTopicSubCommand` / `DeleteSubscriptionGroupSubCommand`) 2. Accept a file or comma-separated list as input for batch names 3. Reuse `MQClientAPIImpl` batch methods directly 4. Print per-item success/failure summary This is a good first-contribution candidate — clear scope, no protocol changes, backend ready. --- *Automated evaluation by RockteMQ-AI* -- 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]
