Skip to content
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

Make connectivity verification not part of driver creation. #609

Merged
merged 3 commits into from
Jul 4, 2019

Conversation

zhenlineo
Copy link
Contributor

Based on top of #587

Copy link
Contributor

@ali-ince ali-ince left a comment

Choose a reason for hiding this comment

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

I would vote for skipping connectivity verification for all and leave it to the user to explicitly call Driver.verifyConnectivity or Driver.verifyConnectivityAsync at his will.

I think there's no value of adding a specific configuration setting for this.

@zhenlineo zhenlineo force-pushed the 2.0-verify-conn branch 5 times, most recently from 923d4b8 to e5f6412 Compare July 3, 2019 21:32
@zhenlineo zhenlineo changed the title Make connectivity verification optional on driver creation. Make connectivity verification not part of driver creation. Jul 4, 2019
Copy link
Contributor

@ali-ince ali-ince left a comment

Choose a reason for hiding this comment

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

LGTM @zhenlineo.

Maybe we can add an explicit warning note that even if the verifyConnectivity throws an exception, the user should still call Driver.close() to clean-up resources.

@zhenlineo zhenlineo merged commit de7dab0 into neo4j:2.0 Jul 4, 2019
@zhenlineo zhenlineo deleted the 2.0-verify-conn branch July 4, 2019 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants