You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Gura (JIRA)" <ji...@apache.org> on 2015/08/14 21:58:45 UTC
[jira] [Comment Edited] (IGNITE-1250) Migrate JDBC driver from Java
client to Ignite node in client mode
[ https://issues.apache.org/jira/browse/IGNITE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697610#comment-14697610 ]
Andrey Gura edited comment on IGNITE-1250 at 8/14/15 7:58 PM:
--------------------------------------------------------------
I implemented most functionality but have some questions:
# I found that Java client based driver allows access to local caches on specified node ({{nodeId}} parameter in JDBC URL). As I understand it is impossible to provide the same functionality in case of Ignite client based driver without running job on specified node. Is this case realy usefull or not? Should we provide access to local caches on server nodes through JDBC driver?
# How we should interpret host and port in JDBC URL if configuration file URL provided? In general configuration file can declare any discovery SPI, including cases that don't require any hosts.
# Should we provide alternative and simple way to configuration Ignite client node without configuration file? If yes, what exactly properties should have this ability? From my point of view, peer class loading is good example of such property. I don't want create configuration file only for customizing one boolean property.
was (Author: agura):
I implemented most functionality but have some question:
# I found that Java client based driver allows access to local caches on specified node ({{nodeId}} parameter in JDBC URL). As I understand it is impossible to provide the same functionality in case of Ignite client based driver without running job on specified node. Is this case realy usefull or not? Should we provide access to local caches on server nodes through JDBC driver?
# How we should interpret host and port in JDBC URL if configuration file URL provided? In general configuration file can declare any discovery SPI, including cases that don't require any hosts.
# Should we provide alternative and simple way to configuration Ignite client node without configuration file? If yes, what exactly properties should have this ability? From my point of view, peer class loading is good example of such property. I don't want create configuration file only for customizing one boolean property.
> 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)