Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Configurable server address resolver #507

Merged
merged 1 commit into from
Jul 2, 2018

Conversation

lutovich
Copy link
Contributor

This PR makes it possible to configure a resolver function used by the routing driver. Such function is used during the initial discovery and when all known routers have failed. Driver already had an internal facility like this which performed a DNS lookup for the hostname of the initial address. This remains the default. Users are now able to provide a custom resolver in the config.

This commit makes it possible to configure a resolver function used by
the routing driver. Such function is used during the initial discovery
and when all known routers have failed. Driver already had an internal
facility like this which performed a DNS lookup for the hostname of
the initial address. This remains the default. Users are now able to
provide a custom resolver in the config.
@lutovich lutovich requested review from technige and zhenlineo June 20, 2018 13:18
Copy link
Contributor

@zhenlineo zhenlineo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nigelsmall Is this resolve function only available for routing driver or also applies to direct driver?

@technige
Copy link
Contributor

There is no reason to only restrict it to routing. There are (a few) use cases where it could be useful for direct too.

@zhenlineo zhenlineo merged commit a53d2b9 into neo4j:1.7 Jul 2, 2018
@lutovich lutovich deleted the 1.7-resolver-func branch July 2, 2018 09:53
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants