[
https://issues.apache.org/jira/browse/IGNITE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702838#comment-14702838
]
Andrey Gura edited comment on IGNITE-1250 at 8/19/15 10:58 PM:
---------------------------------------------------------------
Valentin,
Ok, I'll create thin client based connection in case of {{host:port}} pair
provided and Ignite node based connection in case of {{cfg}} provided.
About URL and parameters. Configuration file URL can have own parameters.
Probably we should use more specific parameter names in order to avoid of
naming conflict. Anyway this format doesn't solve possible problems with URL
specific symbols (i.e. {{?}}, {{=}}).
was (Author: agura):
Valentin,
I don't sure that I correctly understand the meaning of "current driver should
work as it worked before". Do you mean that we should start thin client
instance in case of host based protocol and Ignite client node for config based
protocol?
About URL and parameters. Configuration file URL can have own parameters.
Probably we should use more specific parameter names in order to avoid of
naming conflict.
> 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)
