Skip to content

Use cluster Tarantool client instead of simple one #240

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

Closed
wants to merge 1 commit into from

Conversation

nicktorwald
Copy link

To support fail-over capabilities and node discovery mechanism,
SQLConnection uses TarantoolClusterClient under the hood.

Closes: #199

@nicktorwald nicktorwald force-pushed the nicktorwald/gh-199-cluster-connection branch from 55a278d to 0bfa9b1 Compare November 19, 2019 17:45
@coveralls
Copy link

coveralls commented Nov 19, 2019

Coverage Status

Coverage increased (+0.4%) to 76.039% when pulling f07d2c2 on nicktorwald/gh-199-cluster-connection into 9392133 on master.

@nicktorwald nicktorwald force-pushed the nicktorwald/gh-199-cluster-connection branch from 0bfa9b1 to eacf542 Compare November 19, 2019 18:11
To support fail-over capabilities and node discovery mechanism,
SQLConnection uses TarantoolClusterClient under the hood.

Closes: #199
@nicktorwald nicktorwald force-pushed the nicktorwald/gh-199-cluster-connection branch from eacf542 to f07d2c2 Compare November 19, 2019 18:18
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.

jdbc: support cluster client as the transport
3 participants