[Bug] PulsarAdminBuilderImpl overrides timeout properties passed through config map

[alpreu]

Search before asking

• I searched in the issues and found nothing similar.

Version

master commit id 0e149ef

Minimal reproduce step

PulsarAdminBuilder allows configuration of PulsarAdmin either by using the setters on the builder, or by using the loadConf method that takes in a map of configuration properties.

The properties:

• readTimeout
• connectionTimeout
• requestTimeout

can currently only be correctly applied when using the builder setters (e.g. setReadTimeout) because the build() method accesses these as private fields in PulsarAdminBuilderImpl. If these properties are set through the config map, loadConf does not update these private fields. This results in the config values being ignored and overridden by the default values in PulsarAdminBuilderImpl

What did you expect to see?

Properties should be applied correctly using config map or builder methods,

What did you see instead?

Timeout properties passed in via config map get overwritten by the builders default values.

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!

[github-actions]

The issue had no activity for 30 days, mark with Stale label.