Skip to content
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

feat: enhance StaticNameServerResolver to allow use of gRPC naming sc… #617

Merged

Conversation

lizhanhui
Copy link
Contributor

@lizhanhui lizhanhui commented Oct 8, 2023

…heme compliant endpoints

Which Issue(s) This PR Fixes

Fixes #606

Brief Description

How Did You Test This Change?

@lizhanhui lizhanhui requested a review from aaron-ai October 8, 2023 11:10
@lizhanhui lizhanhui merged commit 920c9ae into apache:master Oct 8, 2023
@lizhanhui lizhanhui deleted the enhance_static_name_server_resolver branch October 9, 2023 02:08
return;
}

std::vector<std::string> segments = absl::StrSplit(name_server_list, absl::ByAnyChar(",;"));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If name_server_list follows gRPC naming scheme, the first element of segments would keep the prefix - 'ipv4:'. I think naming_scheme_.buildAddress will return a wrong result based on this behavior.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@0902horn line #31 returns

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, my bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] RocketMQ5.0代理grpc模式下 c++客户端填入多个endpoint问题
3 participants