[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=14724850#comment-14724850 ] 

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

* If configuration path is ignored, warning should be printed out in log.
* I think we should simplify and get rid of all tasks, at least in case of client execution (this is how the driver will be used in 99% cases). Move the code to separate methods and call it either from task (if needed) or directly from driver classes.
* We don't need to fix old version - it's deprecated (BTW, this should be mentioned in docs). It just needs to work like it worked earlier for compatibility. All fixes go for the new version. I would fix everything in this ticket - there is nothing really complicated.
* I will think about user objects. Let's fix the rest first.

> 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: Valentin Kulichenko
>             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)