[
https://issues.apache.org/jira/browse/IGNITE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702932#comment-14702932
]
Andrey Gura edited comment on IGNITE-1250 at 8/19/15 10:59 PM:
---------------------------------------------------------------
Old driver creates new thin client instance for each connection. It is
unacceptable for Ignite node based driver. Need to reimplement connection
creation logic in order to cache Ignite node instance and share it with
different connections. {{cfg}} can be used as cache key. Ignite node should be
stopped only if no more connections exist for given key.
was (Author: agura):
Old driver creates new thin client instance for each connection. It is
unacceptable for Ignite node based driver. Need to reimplement connection
creation logic in order to cache Ignite node instance and share it with
different connections. {{host}} + {{port}} + {{cfg}} can be used as cache key.
Ignite node should be stopped only if no more connections exist for given key.
> Migrate JDBC driver from Java client to Ignite node in client mode
> ------------------------------------------------------------------
>
> Key: IGNITE-1250
> URL: https://issues.apache.org/jira/browse/IGNITE-1250
> Project: Ignite
> Issue Type: Improvement
> Reporter: Andrey Gura
> Assignee: Andrey Gura
> Fix For: ignite-1.4
>
>
> JDBC driver is still based on legacy Java client which is deprecated, not
> supported and much slower than native query API.
> Needs to replace thin client with an embedded client node.
> See also:
> http://apache-ignite-developers.2346864.n4.nabble.com/JDBC-driver-td2177.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
