[
https://issues.apache.org/jira/browse/IGNITE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706511#comment-14706511
]
Andrey Gura commented on IGNITE-1250:
-------------------------------------
After some thought, I came to the following URL format for new druiver version:
{{jdbc:ignite:cfg://[<params>@]<config_url>}}. Where:
* optional {{params}} part allows to provide {{cache}}, {{nodeId}} and any
other parameters if it will added. {{params}} part has format
{{key1=val1:key2=val2}}. {{@}} is needed for separating driver specific
parameters from configuration URL.
* {{config_url}} represents any valid URL for Ignite configuration file.
This format is good for me for the following reasons:
# it conforms to common rules of URL format (see for example FTP URL with
credentials)
# it allows strictly separate config URL parameters (e.g. HTTP URL with user
specific paramteres) and Ignite cluster parameters (cache, nodeId).
> 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)
