-
Notifications
You must be signed in to change notification settings - Fork 438
Description
BUG REPORT
-
Please describe the issue you observed:
-
What did you do (The steps to reproduce)?
update nameserver version to 4.9.4-snapshot (develop branch)
and use go client to produce message -
What did you expect to see?
produce message success -
What did you see instead?
produce message fail
because Let name server generate valid JSON response when process topic route queries rocketmq#4432 change route info to standard json such as:
{"brokerDatas":[{"brokerAddrs":{"0":"127.0.0.1:10911"}}
the old is:
{"brokerDatas":[{"brokerAddrs":{0:"127.0.0.1:10911"}}
-
-
Please tell us about your environment:
-
What is your OS?
-
What is your client version?
-
What is your RocketMQ version?
-
-
Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):
FEATURE REQUEST
-
Please describe the feature you are requesting.
-
Provide any additional detail on your proposed use case for this feature.
-
Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
-
If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
- sub-task1-issue-number: sub-task1 description here,
- sub-task2-issue-number: sub-task2 description here,
- ...