tree a0d759c0624f197a277910a0f2139a89dda7e599
parent 2d216eb9c903c0d303f132f753f5def8ff9a9fd1
author Enrico Olivelli <eolivelli@gmail.com> 1607727690 +0100
committer GitHub <noreply@github.com> 1607727690 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJf0/pKCRBK7hj4Ov3rIwAAdHIIAAEwlTTUKHu/ORRerbGHpfYy
 8hTKqap1FuRxqIVv57VKxGkAHmbTuB6jnBbJlhBX1Tamh86YOshvpcR3VgKP/GCt
 a33HIGzV/Ul9ccZKy4kmBi3yaZFA4DvtFWFUp4Rvs3gRjIu/APJ+ZZ2oFw73i9CD
 4h1W9ZPh49Tu466g88qa4bcZCRd9daDvVlyEWwuqZQvbb5yJBEFFsJcbsP6VWNDO
 od7+au5cI5QHuproBq5CqbvTwGQ1D7U4ZadZInbzeCxRR1hQWl6UH929KsdlfS7A
 /RZn0VyOh0YZG+NoSMRJVTQn+VyExlilW1KiwUWxrjVzSRJOP7pmOldwXkNSHqM=
 =HH1S
 -----END PGP SIGNATURE-----
 

Allow DNSToSwitchMapping to access BookieAddressResolver

In order to allow Pulsar to leverage BookieId with custom Bookie-To-Rack Mapping (ZkBookieRackAffinityMapping) we need to inject the BookieAddressResolver into it.

There is not way to do it currently because it is created by the BookKeeper client, and we have to inject the same BookieAddressResolver used by the client itself.

*Changes*
- add new setBookieAddressResolver method (use 'default' methods in order to preserve backward compatibility
- call the new method in every point in which we instantiate a DNSToSwitchMapping and when we receive an instance at construction time

*Compatibility*
- this change is 100% compatible with previous versions

Reviewers: Rajan Dhabalia <rdhabalia@apache.org>, Anup Ghatage <ghatage@apache.org>

This closes #2519 from eolivelli/fix/dnsswitch-access-bookieaddress-resolver