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

[Enhancement] Add constructor for ProxyTopicRouteData #7875

Closed
1 task done
drpmma opened this issue Feb 29, 2024 · 1 comment · Fixed by #7876
Closed
1 task done

[Enhancement] Add constructor for ProxyTopicRouteData #7875

drpmma opened this issue Feb 29, 2024 · 1 comment · Fixed by #7876

Comments

@drpmma
Copy link
Contributor

drpmma commented Feb 29, 2024

Before Creating the Enhancement Request

  • I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

Add construtor for ProxyTopicRouteData

Motivation

Add construtor for ProxyTopicRouteData

Describe the Solution You'd Like

Add construtor for ProxyTopicRouteData

Describe Alternatives You've Considered

No

Additional Context

No response

@drpmma drpmma changed the title [Enhancement] Add construtor for ProxyTopicRouteData [Enhancement] Add constructor for ProxyTopicRouteData Feb 29, 2024
drpmma added a commit to drpmma/rocketmq that referenced this issue Feb 29, 2024
@supervate
Copy link
Contributor

If I deploy multi proxy-server and using different port.
e.g p1:8080,p2:8081,p3:8082
Here have a problem that when client call the p1's api to get the topic route info.
This constructor will replace all broker's address port to current proxy's port, like this:
p1:8080,p2:8080,p3:8080.

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