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.

Sign up for GitHub

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

Jump to bottom

jdbc: support cluster client as the transport #199

Open
Totktonada opened this issue Jun 11, 2019 · 3 comments
Open

jdbc: support cluster client as the transport #199

Totktonada opened this issue Jun 11, 2019 · 3 comments
Labels
jdbc optional feature jdbc

Comments

@Totktonada
Copy link
Member

No description provided.

@Totktonada
Copy link
Member Author

I guess this should be simpler now, after #163.

@nicktorwald
Copy link

Agreed. Because a Tarantool client is behind a SQLConnection, we need to elaborate on how a user can pass an initial set of Tarantool instances as well as parameters specific to the cluster config such as discovery function or discovery delay.
I'd consider doing that via a connection string like jdbc:taramtool://host1:port1,host2:port2?clusterDiscoveryFunction=abc&clusterDiscoveryDelayMs=60000&otherParams.

@Totktonada
Copy link
Member Author

I think we should allow to pass all parameters (as usual as well as cluster ones) via properties and URI both.

nicktorwald added a commit that referenced this issue Nov 19, 2019
@nicktorwald
Use cluster Tarantool client instead of simple one
55a278d 
To support fail-over capabilities and node discovery mechanism,
SQLConnection uses TarantoolClusterClient under the hood.

Closes: #199
@nicktorwald nicktorwald mentioned this issue Nov 19, 2019
Closed
nicktorwald added a commit that referenced this issue Nov 19, 2019
@nicktorwald
Use cluster Tarantool client instead of simple one
0bfa9b1 
To support fail-over capabilities and node discovery mechanism,
SQLConnection uses TarantoolClusterClient under the hood.

Closes: #199
nicktorwald added a commit that referenced this issue Nov 19, 2019
@nicktorwald
Use cluster Tarantool client instead of simple one
eacf542 
To support fail-over capabilities and node discovery mechanism,
SQLConnection uses TarantoolClusterClient under the hood.

Closes: #199
nicktorwald added a commit that referenced this issue Nov 19, 2019
@nicktorwald
Use cluster Tarantool client instead of simple one
f07d2c2 
To support fail-over capabilities and node discovery mechanism,
SQLConnection uses TarantoolClusterClient under the hood.

Closes: #199
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
jdbc optional feature jdbc
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use cluster Tarantool client instead of simple one tarantool/tarantool-java
2 participants
@Totktonada @nicktorwald