[
https://issues.apache.org/jira/browse/IGNITE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700780#comment-14700780
]
Valentin Kulichenko edited comment on IGNITE-1250 at 8/18/15 11:29 PM:
-----------------------------------------------------------------------
Andrey,
I don't like this format. And also I just thought that we can't set host and
port in discovery because {{jdbc:ignite://127.0.0.1:50000}} URL should define
thin client to preserve compatibility.
What if we introduce another protocol(s) with path only? For example:
* {{jdbc.ignite.file:/examples/config/example-cache.xml}}
* {{jdbc.ignite.http://localhost/jdbc-config.xml}}
* etc.
What do you think?
was (Author: vkulichenko):
Andrey,
I don't like this format. And also I just thought that we can't set host and
port in discovery because {{jdbc:ignite://127.0.0.1:50000}} URL should define
thin client to preserve compatibility.
What if we introduce another protocol(s) with path only? For example:
* {{jdbc.ignite.cfg.file:/examples/config/example-cache.xml}}
* {{jdbc.ignite.cfg.http://localhost/jdbc-config.xml}}
* etc.
What do you think?
> 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)
