[
https://issues.apache.org/jira/browse/IGNITE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701069#comment-14701069
]
Andrey Gura edited comment on IGNITE-1250 at 8/18/15 4:39 PM:
--------------------------------------------------------------
What do you mean when talk about thin client compatibility? I don't think that
we should support thin Java client anymore. Otherwise we should provide two
different versions of driver.
We still should provide cache name and {{nodeId}} parameter in JDBC URL. I
think that we can do the following:
* Use {{jdbc:ignite://host:port/cache?nodeId=UUID}} format for default
settings. The default settings is:
** VP IP finder
** peer class loading enabled
** {{port}} could be represented as range (e.g. {{47500..47549}})
* Use
{{jdbc:ignite:params:cache=name;nodeId=UUID:cfg:http://localhost/jdbc-config}}
format for configuration files. There is place for optional named parameters
between {{jdbc:ignite:params:}} and {{cfg}} parts. But in this case encoding
problem still exists (parameter values can contain symbols like {{=}} and
{{;}}).
Thoughts?
was (Author: agura):
What do you mean when talk about thin client compatibility? I don't think that
we should support thin Java client anymore. Otherwise we should provide two
different versions of driver.
We still should provide cache name and {{nodeId}} parameter in JDBC URL. I
think that we can do the following:
* Use {{jdbc:ignite://host:port/cache?nodeId=UUID}} format for default
settings. The default settings is:
** VP IP finder
** peer class loading enabled
** {{port}} could be represented as range (e.g. {{47500..47549}})
* Use
{{jdbc:ignite:params:cache=name;nodeId=UUID:cfg:http://localhost/jdbc-config}}
format for configuration files. There is place for optional named parameters
between {{jdbc:ignite:params:}} and {{cfg}} parts. But in this case encoding
problem still exists (parameter values can contain symbols like {{=}} and
{{;}}).
> 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)
