Re: xml config can not be used in jdbs and user code simultaneously

[Andrey Gura]

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 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.
> >
>

[jira] [Created] (IGNITE-5790) Xml config can not be used in jdbs and user code simultaneously

[Mikhail Cherkasov (JIRA)]

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: Ignite
  Issue Type: Bug
  Components: jdbc
Affects Versions: 2.1
Reporter: Mikhail Cherkasov
Assignee: Mikhail Cherkasov
 Fix For: 2.1


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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: xml config can not be used in jdbs and user code simultaneously

[Vladimir Ozerov]

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 :
> 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.
>

xml config can not be used in jdbs and user code simultaneously

[Mikhail Cherkasov]

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.