We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ClientConfig#getNamesrvAddr()
public String getNamesrvAddr() { if (StringUtils.isNotEmpty(namesrvAddr) && NameServerAddressUtils.NAMESRV_ENDPOINT_PATTERN.matcher(namesrvAddr.trim()).matches()) { return NameServerAddressUtils.getNameSrvAddrFromNamesrvEndpoint(namesrvAddr); } return namesrvAddr; }
If the format is "http://xxx.xx.xx:9876; " with a space after it, 2 addresses will be parsed out;
如果格式为"http://xxx.xx.xx:9876; " 后面带有空格的时候,会解析出来2个地址;
解析的时候 可以把nameAddr处理一下
When parsing, you can handle nameAddr
public String getNamesrvAddr() { if (StringUtils.isNotEmpty(namesrvAddr) && NameServerAddressUtils.NAMESRV_ENDPOINT_PATTERN.matcher(namesrvAddr.trim()).matches()) { return NameServerAddressUtils.getNameSrvAddrFromNamesrvEndpoint(namesrvAddr.trim()); } return namesrvAddr; }
.
No response
The text was updated successfully, but these errors were encountered:
Enhancement getNamesrvAddr trim apache#7252
8f27cac
This issue is stale because it has been open for 365 days with no activity. It will be closed in 3 days if no further activity occurs.
Sorry, something went wrong.
This issue was closed because it has been inactive for 3 days since being marked as stale.
Successfully merging a pull request may close this issue.
Before Creating the Enhancement Request
Summary
ClientConfig#getNamesrvAddr()
If the format is "http://xxx.xx.xx:9876; " with a space after it, 2 addresses will be parsed out;
如果格式为"http://xxx.xx.xx:9876; " 后面带有空格的时候,会解析出来2个地址;
解析的时候 可以把nameAddr处理一下
When parsing, you can handle nameAddr
Motivation
.
Describe the Solution You'd Like
.
Describe Alternatives You've Considered
.
Additional Context
No response
The text was updated successfully, but these errors were encountered: