yyqdbngt opened a new issue, #2244: URL: https://github.com/apache/rocketmq-dashboard/issues/2244
## Problem The shared Apache provider filter treats every topic beginning with `CID_`, `broker_`, `BenchmarkTest`, `SCHEDULE_TOPIC_`, or uppercase `RMQ_SYS_` as a system topic. Those prefix rules are broader than RocketMQ's current canonical `TopicValidator.isSystemTopic` definition. Valid user topics such as `CID_orders`, `broker_events`, `BenchmarkTestOrders`, and `SCHEDULE_TOPIC_orders` are therefore silently removed from topic lists and dashboard totals even though RocketMQ accepts them as ordinary topics. This behavior was centralized by #1408 to make providers consistent. The providers are now consistent, but the shared rule itself still hides lookalike user topics. ## Expected behavior - Use RocketMQ's canonical system-topic definition for exact names and the lowercase `rmq_sys_` prefix. - Continue hiding retry and dead-letter topics. - Continue hiding exact live broker names where the provider supplies them. - Do not hide valid user topics solely because their names resemble historical/internal prefixes. ## Proposed scope Delegate canonical classification to `TopicValidator`, preserve the Dashboard-specific retry, DLQ, and live-broker cases, and add regression tests for canonical topics and valid lookalikes. ## Duplicate check Reviewed #1407/#1408 and the later consolidated tests in #2034. They introduced and verified the shared broad prefixes but do not correct the mismatch with current RocketMQ `TopicValidator`. No open pull request changes the shared filter or its test. -- 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]
