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

ASF GitHub Bot commented on IGNITE-7743:
----------------------------------------

GitHub user pavel-kuznetsov opened a pull request:

    https://github.com/apache/ignite/pull/4336

    IGNITE-7743: applied changes from outdated pull request

    Fixed outdated pull request https://github.com/apache/ignite/pull/3761/files

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-7743-new

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4336.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4336
    
----
commit da499c0d80df0b8ca48cb07797e0e6a2ce0f581b
Author: Pavel Kuznetsov <palmihal@...>
Date:   2018-07-09T17:59:19Z

    IGNITE-7743: applied changes from outdated pull request

----


> 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.7
>
>
> 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)

Reply via email to