Aias00 opened a new issue, #1015: URL: https://github.com/apache/rocketmq-dashboard/issues/1015
## Problem\nSeveral live metadata mappings currently misrepresent RocketMQ state:\n- Topic create/update always writes permission , ignoring the requested/current permission.\n- Topic route output selects an arbitrary broker address instead of preferring the master.\n- Topic consumer output hard-codes .\n- Consumer-group enrichment maps to , although these are different dimensions.\n- Subscription filter mode maps to SQL and falls back to TAG for other values, including SQL92.\n\n## Expected behavior\nExpose the corresponding RocketMQ metadata without rewriting permissions or conflating message model, push/pop mode, and filter expression type.\n\n## Acceptance criteria\n- Existing topic permissions are preserved on update and validated on create.\n- Route rows use master broker addresses when available.\n- Consumer and subscription fields accurately reflect the source protocol values.\n- Regression tests cover BROADCASTING, SQL92/CLASS_FILTER, and non-RW topic permissions. -- 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]
