[
https://issues.apache.org/jira/browse/IGNITE-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129007#comment-16129007
]
ASF GitHub Bot commented on IGNITE-5790:
----------------------------------------
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/2460
IGNITE-5790 SQL: Append UUID to names of Ignite instances opened by JDBC
All Ignite instances created by Jdbc driver should now be either named or
appended with ignite-jdbc-driver-UUID to avoid conflicting with instances
created in other places.
Had to inline parts of IgnitionEx.start() to apply changes to every
decision branch.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alamar/ignite ignite-5790
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2460.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2460
----
commit 05c45747750e10fc094a09a2189f895ffd768520
Author: Ilya Kasnacheev <[email protected]>
Date: 2017-08-16T15:26:43Z
IGNITE-5790 SQL: Append UUID to names of Ignite instances opened by JDBC.
----
> 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: Ilya Kasnacheev
> 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)
