[ https://issues.apache.org/jira/browse/IGNITE-8100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Kasnacheev resolved IGNITE-8100. ------------------------------------- Resolution: Duplicate Fix Version/s: 2.8 > jdbc getSchemas method could miss schemas for not started remote caches > ----------------------------------------------------------------------- > > Key: IGNITE-8100 > URL: https://issues.apache.org/jira/browse/IGNITE-8100 > Project: Ignite > Issue Type: Bug > Components: jdbc, sql > Reporter: Pavel Kuznetsov > Priority: Major > Fix For: 2.8 > > > On jdbc side we have > org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getSchemas(java.lang.String, > java.lang.String) > on the server side result is constructed by this: > {noformat} > for (String cacheName : ctx.cache().publicCacheNames()) { > for (GridQueryTypeDescriptor table : ctx.query().types(cacheName)) { > if (matches(table.schemaName(), schemaPtrn)) > schemas.add(table.schemaName()); > } > } > {noformat} > see > org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler#getSchemas > If we havn't started cache(with a table) on some remote node, we will miss > that scheme. -- This message was sent by Atlassian JIRA (v7.6.3#76005)