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/09/25 13:54:01 UTC

[jira] [Updated] (IGNITE-6481) JDBC v2: must not use a cache to query Ignite

     [ https://issues.apache.org/jira/browse/IGNITE-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Ozerov updated IGNITE-6481:
------------------------------------
    Fix Version/s:     (was: 2.3)

> JDBC v2: must not use a cache to query Ignite
> ---------------------------------------------
>
>                 Key: IGNITE-6481
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6481
>             Project: Ignite
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 2.1
>            Reporter: Taras Ledkov
>
> Now the {{cache}} parameter is required for the JDBC v2 driver.
> But Ignite internal API allows execute SQL query with nothing cache specified.
> {{cache}} parameter must be optional (for compatibility with previous versions)
> {{schema}} parameter must be added to allow specify the schema at the connection string.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)