ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Valentin Kulichenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1250) Migrate JDBC driver from Java client to Ignite node in client mode
Date Wed, 19 Aug 2015 06:41:45 GMT

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

Valentin Kulichenko commented on IGNITE-1250:


We can have one driver class and define the protocol that should be used in the URL. Anyway,
current driver should work as it worked before.

As for configuration, how about supporting parameters like this (BTW, they can also be provided
in additional Properties):
* jdbc.ignite.file:/examples/config/example-cache.xml?cache=cacheName&nodeId=UUID

I would like to avoid encoding issue, it's really user-unfriendly...

> 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

View raw message