Aias00 commented on issue #1982:
URL:
https://github.com/apache/rocketmq-dashboard/issues/1982#issuecomment-5294056221
Additional verification details:
- Affected baseline: rocketmq-studio at eb44e159 (also reproduced before the
fix on the original Issue baseline).
- Prerequisite: an Apache RocketMQ 5.x instance reachable from Studio.
- Steps:
1. Select the Apache instance.
2. Create or explicitly update a Topic with type FIFO, DELAY, TRANSACTION,
or LITE.
3. Capture the TopicConfig passed to
DefaultMQAdminExt#createAndUpdateTopicConfig.
4. Inspect TopicConfig#getAttributes().
- Actual: the attributes map is empty, so the Broker receives no
+message.type attribute while Studio stores the selected type locally.
- Expected: the config contains +message.type=<selected type>; an update
that omits type preserves the Broker type.
- Logs/stack trace: none is produced; this is an incorrect Admin request
payload, reproduced with focused unit tests that capture the submitted
TopicConfig.
The active fix is #1983, which covers both create and update paths and
closes this Issue. The earlier duplicate implementation #2060 is closed.
--
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]
