ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-7743) JDBC driver allows to connect to non existent schema
Date Tue, 27 Mar 2018 15:13:00 GMT

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

Pavel Kuznetsov updated IGNITE-7743:
------------------------------------
    Labels: usability  (was: )

> JDBC driver allows to connect to non existent schema
> ----------------------------------------------------
>
>                 Key: IGNITE-7743
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7743
>             Project: Ignite
>          Issue Type: Bug
>          Components: jdbc, sql
>    Affects Versions: 2.3
>            Reporter: Valentin Kulichenko
>            Assignee: Pavel Kuznetsov
>            Priority: Major
>              Labels: usability
>             Fix For: 2.5
>
>
> Currently, if one creates a cache without DDL (via {{QueryEntity}} or {{indexedTypes}}),
separate schema for this cache is created. Schema name is case sensitive, so to connect to
it with JDBC driver, it's required to provide the name in quotes. Here is how it looks like
in SqlLine:
> {noformat}
> ./bin/sqlline.sh -u jdbc:ignite:thin://127.0.0.1/\"CacheQueryExamplePersons\"
> {noformat}
> However, if name is provided without quotes, driver still connects, but then fails with
a very unclear exception when a query is executed:
> {noformat}
> ./bin/sqlline.sh -u jdbc:ignite:thin://127.0.0.1/CacheQueryExamplePersons{noformat}
> This is a huge usability issue. We should disallow connections to schema that does not
exist, throw exception in this case. Exception should provide proper explanation how to connect
properly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message