btlqql opened a new issue, #2248: URL: https://github.com/apache/rocketmq-dashboard/issues/2248
## Problem Apache topic route permissions are bit masks: READ is 4, WRITE is 2, and INHERIT is 1. Studio currently maps permissions with exact integer comparisons for 6, 4, and 2. Queue permissions that include INHERIT are therefore misreported. For example, READ|INHERIT (5) is shown as read-write instead of read-only, and WRITE|INHERIT (3) is shown as read-write instead of write-only. ## Expected behavior - Determine readability and writability from the permission bits. - Map 4/5 to RO, 2/3 to WO, and 6/7 to RW. - Preserve the existing fallback for masks that have neither read nor write bits because the current view model has no inaccessible value. - Keep broker address and queue-count mapping unchanged. ## Proposed scope Use RocketMQ's official `PermName` helpers in the Apache metadata provider and add route-level parameterized coverage for permission masks and the surrounding route fields. ## Duplicate check Searched open and closed issues and pull requests for QueueData permission bits, INHERIT route permissions, and topic permission mapping. No matching implementation was found, and no current pull request targeting `rocketmq-studio` changes the provider 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]
