First solution is bad idea because client could be closed by driver while
user code still uses this client.
17 июля 2017 г. 12:49 PM пользователь "Vladimir Ozerov" <
voze...@gridgain.com> написал:
> I would say this is a usability issue, please file a ticket. But why one
> need to use JDBC when
Mikhail Cherkasov created IGNITE-5790:
-
Summary: Xml config can not be used in jdbs and user code
simultaneously
Key: IGNITE-5790
URL: https://issues.apache.org/jira/browse/IGNITE-5790
Project
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
wrote:
> Hi all,
>
> when user uses the same xml config for jdbc driver and for his own ignite
> instance there can be :
> jav
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
becau
