[ https://issues.apache.org/jira/browse/IGNITE-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425230#comment-16425230 ]
Taras Ledkov commented on IGNITE-7743: -------------------------------------- [~pkouznet], my comments: 1. What about compatibility tests? 2. Javadoc for {{GridQueryProcessor#hasSchema}} 3. {{JdbcThinConnectionSchemaTest}} at the some tests: {code} int srvPort = portOf(clientNode); int clPort = portOf(clientNode); {code} is it OK? 4. {{JdbcThinConnectionSchemaTest}} javadoc for member; 5. Why we need next protocol version after 2.5.0? There is nothing release with 2.5.0 protocol version. > 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)