[jira] [Commented] (IGNITE-10118) JDBC v2: metadata.getSchemas returns cache names instead of schema names

["Pavel Kuznetsov (JIRA)" <ji...@apache.org>]

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

Pavel Kuznetsov commented on IGNITE-10118:
------------------------------------------

[~vozerov] looked at the this issue patch. Due to IGNITE-9989 introduced big change into jdbc v2 metadata, it fixed this issue as well; Also it introduced the same test.
Closing as duplicate of 9989 

> JDBC v2: metadata.getSchemas returns cache names instead of schema names
> ------------------------------------------------------------------------
>
>                 Key: IGNITE-10118
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10118
>             Project: Ignite
>          Issue Type: Bug
>          Components: jdbc, sql
>    Affects Versions: 2.6
>            Reporter: Pavel Kuznetsov
>            Assignee: Pavel Kuznetsov
>            Priority: Major
>
> jdbc v2 returns list of cache names instead of list of schemas.
> It is correct only if we have a cache and table created in it using cache API.
> If we create tables using ddl we expect to see "PUBLIC" schema name in results of {{connection.getMetadata().getSchemas()}} not "SQL_PUBLIC_TABLENAME"



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