Open Robustshouhualee opened 3 months ago
please look this issue。 @xuthus5 @tuteng @zhongxp1219
Could you help to support this? thanks. @tuteng @shoothzj
Do you want to make the ClientOptions.ListenerName
parameter support configurable?
https://github.com/apache/pulsar-client-go/blob/2d51323103a65ba522dc73f56f052cc81d663245/pulsar/client.go#L133
@Robustshouhualee
Do you want to make the
ClientOptions.ListenerName
parameter support configurable? https://github.com/apache/pulsar-client-go/blob/2d51323103a65ba522dc73f56f052cc81d663245/pulsar/client.go#L133 @Robustshouhualee
It seems that the pulsar go client has support for configuring ListenerName
, what should we do in this project if we want to configure it?
Change the struct pulsarConfig
and add a field such as:
ListenerName string `config:"listener_name"`
change function initOptions
add condition:
if config.ListenerName != "" {
clientOptions.ListenerName = config.ListenerName
}
then change xxx.yaml add listener_name = {listener_name } to test.
backgroup
This tool currently does not support the configuration of :multiple converted listeners for pulsar. When the client's network environment is a combination of internal and external IPs, some network environments do not support writing to pulsar。
expect
Expect community authors to support this feature,thx。
Reference
https://pulsar.apache.org/docs/next/concepts-multiple-advertised-listeners/