You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Kasnacheev (JIRA)" <ji...@apache.org> on 2018/04/02 13:31:00 UTC

[jira] [Created] (IGNITE-8107) Drop cache with SQL table, recreate table on a different cache - cluster fails to activate

Ilya Kasnacheev created IGNITE-8107:
---------------------------------------

             Summary: Drop cache with SQL table, recreate table on a different cache - cluster fails to activate
                 Key: IGNITE-8107
                 URL: https://issues.apache.org/jira/browse/IGNITE-8107
             Project: Ignite
          Issue Type: Bug
          Components: sql
            Reporter: Ilya Kasnacheev


This is a bizzare twist on IGNITE-8021

Imagine you have a cache "tbl" created by public API with corresponding table "tbl".TBL. You also have PDS. Drop this cache, CREATE TABLE TBL with corresponding SQL_PUBLIC_TBL cache. It would work, but if you shut down cluster and try to bring it online, it will fail to activate:

{code}SchemaOperationException [code=3, msg=Table already exists: TBL]{code}






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