Frun1na opened a new issue, #4919: URL: https://github.com/apache/rocketmq-dashboard/issues/4919
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository and believe that this is not a duplicate. - [x] This is a defect in RocketMQ Studio, not a usage question and not a defect in another Apache RocketMQ repository. - [x] I can reproduce this on the current `master` branch, or I have stated the exact version I am running below. ### Studio Version branch: `rocketmq-studio` git commit id: `1ef5d860` (upstream tip at the time of the report) deployed as: built from source ### Runtime Environment Verified by code tracing and unit tests on `rocketmq-studio` @ `1ef5d860` (vitest for `web/`, JUnit for `server/`), not against a specific browser or deployment. ### Connected RocketMQ Cluster Not cluster-specific: the defect lives in the code path and reproduces on any deployment where the trigger condition below holds. ### Describe the Bug Per the query failure grading contract, business-empty results (topic route absent) must return 200 with empty data, while RPC-level failures are the only ones that error. The key query path grades `NO_MESSAGE` as empty but not `TOPIC_NOT_EXIST`, so a query against a just-deleted topic surfaces a gateway error. ### Steps to Reproduce 1. Create a topic, send a message with a key, then delete the topic (or pick any topic whose route is gone). 2. On the message page, run a Key query with that topic. 3. The API returns 502 `Failed to query messages by key: ...`. ### What Did You Expect to See? 200 with an empty list, exactly like the topic-mode query (`queryByTopic`) already grades `TOPIC_NOT_EXIST` / `NO_MESSAGE`. ### What Did You See Instead? 502 gateway error for a business-empty situation. -- 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]
