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

["Ilya Kasnacheev (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127530#comment-16127530 ] 

Ilya Kasnacheev commented on IGNITE-5790:
-----------------------------------------

I'm afraid we can't use solution 1).

We can mind the lifecycle of Ignite we've got or started, but JDBC driver can't make sure Ignite that was already existing, and now shared, isn't closed while still being needed by JDBC.

2) should probably be implemented, with appended UUID as in loadConfiguration() method but in more generic way.

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