-
Notifications
You must be signed in to change notification settings - Fork 900
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
RocketMQProperties#nameServer
should offer a more user-friendly format
#8
Comments
This is a good suggestion, at present most of the RocketMQ users get used to define multiple name-servers with the single line property. I incline to defer this enhancement. |
@snicoll Could you help to review and find out the remaining problems or trivial polish, we would release the 2.0.1, hoping including all improvements. |
@vongosling are you asking in the context of this particular issue or globally? If you're asking globally, you can reach out by email (available on my profile). If you're asking in the context of this issue, I am afraid I didn't get the request. |
@snicoll Hah, I wonder could you have any other comments in rocketmq-spring-boot-starter. I am not sure whether your colleague aclement request you to help the community review the code. Anyway, I very appreciate your guys' review help :-) |
Got it. Yes, I am working with Andy. I'll do one more pass today. |
May I ask why this issue was closed? I don't see any change on |
Hi @snicoll, you can reopen this issue, I will submit a PR to slove this issue and ensure backward compatibility. |
Thank you but I don’t have the rights to reopen it. |
@snicoll Could you help to review this improvement? YAML and list style(rocketmq.name-server[0]=XXX, rocketmq.name-server[1]=XXX. Or rocketmq.name-server= XXX) are all supported and vefified now. |
The
nameServer
property ultimately maps toClientConfig#setNamesrvAddr
that requires ahost:port
pair separated by;
I think it would be nicer to not expose that complexity back to the configuration. Rather, the configuration should expose a
List<String>
where each item represent ahost:port
pair.There are several advantages to this:
servers
to express it is a listTaking this into consideration (+ #9) the property can be configured as follows:
The text was updated successfully, but these errors were encountered: