I would say this is a usability issue, please file a ticket. But why one need to use JDBC when already on Ignite node?
On Fri, Jul 14, 2017 at 4:30 PM, Mikhail Cherkasov <mcherka...@gridgain.com> wrote: > Hi all, > > when user uses the same xml config for jdbc driver and for his own ignite > instance there can be : > java.sql.SQLException: Failed to start Ignite node. > Caused by: class org.apache.ignite.IgniteCheckedException: Ignite instance > with this name has already been started: CustomeIgniteName > > because JDBC creates separate ignite instance, while user already has one > with the same name. > > Of course that can be easily workarounded, user can support two configs or > create jdbc connect first and then use Ignition.getOrStart(). > > However it's inconvenient for user and should be treated as usability > issue. > I see 2 solutions: > 1) jdbc driver should use Ignition.getOrStart() > 2) jdbc driver should connection string as ignite name. > > Thoughts? > > -- > Thanks, > Mikhail. >
