-
Notifications
You must be signed in to change notification settings - Fork 38
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
4.x: drop ResolverProviderTest
in favor of org.burningwave.tools.net.HostResolutionRequestInterceptor
#351
Comments
ResolverProviderTest
in favor of org.burningwave.tools.net.HostResolutionRequestInterceptor
ResolverProviderTest
in favor of org.burningwave.tools.net.HostResolutionRequestInterceptor
ResolverProviderTest
in favor of org.burningwave.tools.net.HostResolutionRequestInterceptor
I am not sure if we can do the mapping of single hostname to multiple IPs with that |
We 100% need that, can you double check on that ? |
The MappedHostResolver seems to use a normal Map and assume that single hostname can be mapped to single ip. Multiple hostnames can point to the same ip.
However the return type here and interface signatures suggest that it should be possible to implement another version of HostResolver that would use a multimap (or map that accepts a list of addresses as a value) |
@Bouncheck , can you please check if your suggestion true or not. |
I'll make a quick proof of concept |
It's working on a simple example.
Produces the following output
|
@Bouncheck , great, can you please make s PR to move to org.burningwave.tools.net.HostResolutionRequestInterceptor |
Yes, already on it |
Created PR #354 |
Closed at #354. |
At #332 we have introduced a
ResolverProvider
toscylla-4.x
that allows us to hook to dns resolution logic in the driver.At #344 @Bouncheck found better solution (
org.burningwave.tools.net.HostResolutionRequestInterceptor
) to do that we exact same limitations, and it does not need hooking to driver code to achieve that.So, let's drop
ResolverProvider
onscylla-4.x
and useorg.burningwave
instead, all the tests stays in the code.It worth to mention that
org.burningwave.tools.net.HostResolutionRequestInterceptor
works just fine on java-11, so it is a "future proof".The text was updated successfully, but these errors were encountered: