You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/05/10 09:22:04 UTC

[jira] [Commented] (IGNITE-3771) JDBC driver tries to initialize the cache store

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

Vladimir Ozerov commented on IGNITE-3771:
-----------------------------------------

[~vkulichenko], as we have DML now, this behavior makes sense. I propose to close the ticket as won't fix. Agree?

> JDBC driver tries to initialize the cache store
> -----------------------------------------------
>
>                 Key: IGNITE-3771
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3771
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 1.7
>            Reporter: Valentin Kulichenko
>             Fix For: 2.1
>
>
> Since JDBC driver is read-only, the cache store doesn't make sense for it, but having it in cache configuration leads to issues like described in [1]. We should implement a mechanism to ignore such things on JDBC driver (probably use daemon node?).
> [1] http://apache-ignite-users.70518.x6.nabble.com/DiscoveryMetricsProvider-implementation-td7312.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)