[
https://issues.apache.org/jira/browse/IGNITE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718627#comment-14718627
]
Andrey Gura commented on IGNITE-1250:
-------------------------------------
* Driver will just ignore cfg path. Of course, user can add {{ignite.jdbc.cfg}}
property and pass properties to {{connect}} method, but it property isn't
documented and builds from URL. We can change {{connect}} method in order to
check URL prefix, not {{PROP_CFG}} property before connection instance creation.
* {{JdbcConnectionValidationTask}} checks that at least one node in cluster has
cache with given name (or default). I think it should be optimized for case
with {{nodeId}} parameter provided.
* Good point. I'll optimize it. May be create new ticket for this task, because
it related with both driver versions?
* Ok. May be we should create new ticket for this task, because it related with
both driver versions?
* Ok. May be we should create new ticket for this task, because it related with
both driver versions?
* Ok. May be we should create new ticket for this task, because it related with
both driver versions?
* Yes, we can close cursor with result set. Good point!
* Ok. May be we should create new ticket for this task, because it related with
both driver versions?
* You are right. Unsuccessful refactoring :) I'll fix it.
* Yes, {{JdbcUtils.sqlType}} call is redundant in {{JdbcResultSet.next}}. Will
fix.
* Yes, it can cause issues. Will fix.
* Ok. May be we should create new ticket for this task, because it related with
both driver versions?
* It should be discussed. Also this problem is actual for both driver versions.
> 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)
