[IGNITE-8100] jdbc getSchemas method could miss schemas for not started remote caches

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 2.8
• Component/s: jdbc, sql
• Assignee: Unassigned
• Reporter: Pavel Kuznetsov
• Created: 02/Apr/18 10:48
• Updated: 24/Sep/20 10:18
• Resolved: 22/Feb/19 16:58

Description

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:

for (String cacheName : ctx.cache().publicCacheNames()) {
        for (GridQueryTypeDescriptor table : ctx.query().types(cacheName)) {
            if (matches(table.schemaName(), schemaPtrn))
               schemas.add(table.schemaName());
        }
}

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.

Issue Links

• duplicates: IGNITE-6173 SQL: do not start caches on client nodes
• is related to: IGNITE-8060 Sqline creating tables on client nodes works incorrect in case of node's shutdown
• is related to: IGNITE-8055 Sqline command !tables works incorrect for client node
• relates to: IGNITE-13482 Client node cannot ALTER TABLE if it was created on a different node