-
Notifications
You must be signed in to change notification settings - Fork 534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#5538] message type was missing from TopicConfigInfo in rocketmq-das… #158
base: master
Are you sure you want to change the base?
Conversation
@Oliverwqcwrw Please review this when available |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The page also needs to add messageType
By the way, it's better to test locally if messageType is displayed successfully, and it would be nice to add a screenshot of messageType displayed successfully
Hi @Oliverwqcwrw sorry for delaying this. |
|
@Oliverwqcwrw from where I have to add message type in frontend ? |
@Koudinka I have already added mesageType in TopicConfigInfo. I don't understand Oliver's first point The page also needs to add messageType |
The page is here |
@Oliverwqcwrw sorry for delaying this. |
} | ||
|
||
public void setMessageType(TopicConfig topicConfig) { | ||
this.messageType = topicConfig.getAttributes().getOrDefault("message.type", ""); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is better to set NORMAL when the message type is empty,
WDYT
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes right that will be more verbose.
@Oliverwqcwrw done please check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are two small problems outside of the presentation
- It doesn't take effect when creating a topic with a message type; for example, it still remains as NORMAL when I create a FIFO topic.
- It would be more user-friendly to let the user choose from a message type drop-down box when creating a topic.
There should update TopicConfig attributes when create or update topic . |
What is the purpose of the change
#5538 - issue reported for examine Topic Config Query not returning message.type in query result.