[
https://issues.apache.org/jira/browse/IGNITE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709321#comment-14709321
]
Andrey Gura commented on IGNITE-1250:
-------------------------------------
Implemented.
Proper connection implementation will be created accordingly to provided JDBC
connection URL.
If URL has {{jdbc:ignite://host:port/cache?nodeId=UUID}} format then Ignite
Java client based connection will be created.
If URL has {{jdbc:ignite:cfg://[<params>@]<config_url>}} format then Ignite
client node based connection will be created.
Ignite client based connection implementation is placed in
{{org.apache.ignite.internal.jdbc2}} packacge. It is internal package, so it
can be renamed with out affecting client code.
PR created https://github.com/apache/ignite/pull/29
Please review.
> 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)
