[ https://issues.apache.org/jira/browse/IGNITE-22213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Belyak updated IGNITE-22213: -------------------------------------- Priority: Major (was: Minor) > Schema PUBLIC not found for a short time right after start using JDBC > --------------------------------------------------------------------- > > Key: IGNITE-22213 > URL: https://issues.apache.org/jira/browse/IGNITE-22213 > Project: Ignite > Issue Type: Bug > Components: sql > Affects Versions: 3.0 > Reporter: Alexander Belyak > Priority: Major > > 1) Start cluster, > 2) Init cluster, > 3) {color:#1d1c1d}Without waiting expected topology, connect using JDBC{color} > 4) Create table > Expected result: table successfully created > Actual result: error > {noformat} > java.sql.SQLException: Schema not found [schemaName=PUBLIC] at > org.apache.ignite.internal.jdbc.proto.IgniteQueryErrorCode.createJdbcSqlException(IgniteQueryErrorCode.java:57) > at > org.apache.ignite.internal.jdbc.JdbcStatement.execute0(JdbcStatement.java:154) > at > org.apache.ignite.internal.jdbc.JdbcStatement.executeQuery(JdbcStatement.java:111){noformat} > {color:#1d1c1d}After cluster is fully initialized (logical topology meets > expectations), it fixes.{color} > {color:#1d1c1d}If the cluster is not ready to process the connection - it > shouldn't accept it. Or wait until metadata schema available on request > processing.{color} > > -- This message was sent by Atlassian Jira (v8.20.10#820010)