jdbc: support cluster client as the transport #199

Activity

1. Totktonada

   added

   jdbc

   jdbc optional feature

   on Jun 11, 2019
2. Totktonada commented on Nov 6, 2019

   

   Totktonada

   on Nov 6, 2019

   Author

   More actions

   I guess this should be simpler now, after #163.
3. nicktorwald commented on Nov 6, 2019

   

   nicktorwald

   on Nov 6, 2019

   More actions

   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.
4. Totktonada commented on Nov 6, 2019

   

   Totktonada

   on Nov 6, 2019

   Author

   More actions

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

   added 4 commits that reference this issue on Nov 19, 2019

   Use cluster Tarantool client instead of simple one

   ...

   This issue will close once commit 55a278d is merged into the 'master' branch.

   55a278d

   Use cluster Tarantool client instead of simple one

   ...

   This issue will close once commit 0bfa9b1 is merged into the 'master' branch.

   0bfa9b1

   Use cluster Tarantool client instead of simple one

   ...

   This issue will close once commit eacf542 is merged into the 'master' branch.

   eacf542

   Use cluster Tarantool client instead of simple one

   ...

   This issue will close once commit f07d2c2 is merged into the 'master' branch.

   f07d2c2