lizhimins commented on issue #3291: URL: https://github.com/apache/rocketmq-dashboard/issues/3291#issuecomment-5581001945
Resolved by #3294, merged into `rocketmq-studio` as 895498a7. The Client Connections page now forwards `clusterId` and `type` to the backend query parameters that already existed but were never sent, refetches when either filter changes, resets pagination to page 1 on filter change, and derives statistics, diagnostics, table rows and the CSV export from the server-filtered response instead of filtering a full inventory in the browser. Two follow-on details worth noting: - The cluster selector no longer collapses. It previously derived its options solely from `connections.map(c => c.clusterName)`, so filtering one response made the other clusters disappear from the dropdown and an unfiltered `clusterName` could contribute a null option. It now unions the registry cluster names (`registryClusters` → `nsClusterName`) with the connection cluster names, both with `.filter(Boolean)`. - Type filter options reuse the existing `typeConfig` labels (`Producer` / `Consumer`), which are language-neutral technical identifiers, so no new translation keys were needed. Because this repository squash-merges against `rocketmq-studio` rather than the default branch, GitHub does not auto-close issues referenced in a PR body; closing manually. -- 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]
