[jira] [Commented] (IGNITE-1250) Migrate JDBC driver from Java client to Ignite node in client mode

["Valentin Kulichenko (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699013#comment-14699013 ] 

Valentin Kulichenko commented on IGNITE-1250:
---------------------------------------------

Andrey,

My comments are below.

# I think we should implement this in the same way as with the thin client. If {{nodeId}} is set you can simply execute a remote job instead of executing locally. I think the same code can be reused, just make sure that the result is properly serialized.
# We can create a default configuration with VM IP finder in discovery and use the provided host and port. Otherwise, user has to provide a configuration file. BTW, can you provide an example of how the url with configuration file path as a parameter will look like?
# I don't like this. User should run with the same configuration everywhere, otherwise he will likely have consistency issues. This is error-prone. The only useful shortcut I see here is host:port provided in the URL (as described above).

> 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)