CREATE … CLONE command: Cloning databases and schemas that contain hybrid tables (Pending)¶

Given that hybrid tables do not currently support cloning, note the following behavior when you attempt to clone a database or a schema that contains hybrid tables:

Before the change:

All CREATE DATABASE … CLONE and CREATE SCHEMA … CLONE commands silently skip hybrid tables if any exist in the specified database or schema.

After the change:

CREATE SCHEMA … CLONE commands return an error if any hybrid tables exist in the specified schema. For example, the following command fails:

CREATE SCHEMA dst CLONE src;

Copy

392105 (0A000): SQL execution error: Cloning a SCHEMA which contains a HYBRID TABLE is unsupported. To perform the clone while skipping HYBRID TABLES, append the `IGNORE HYBRID TABLES` syntax to your DDL.

The error prompts you to run the command using the IGNORE HYBRID TABLES parameter. When you use this parameter, the command will create the cloned schema but skip any hybrid tables. For example:

CREATE SCHEMA dst CLONE src IGNORE HYBRID TABLES;

Copy

CREATE DATABASE … CLONE commands that use Time Travel and specify the time with the STATEMENT parameter return an error if any hybrid tables exist in the specified database. For example, the following command fails:

CREATE DATABASE dst CLONE src
  BEFORE (STATEMENT => '01b7676a-0002-d908-0000-a99500f6e00e');

Copy

392106 (0A000): SQL execution error: Time Travel cloning a DATABASE which contains a HYBRID TABLE, when specifying the time via a `STATEMENT` is unsupported. To perform the clone while skipping HYBRID TABLES, append the `IGNORE HYBRID TABLES` syntax to your DDL.

The error prompts you to run the command using the IGNORE HYBRID TABLES parameter. When you use this parameter, the command will create the cloned database but skip any hybrid tables. For example:

CREATE DATABASE dst CLONE src
  BEFORE (STATEMENT => '01b7676a-0002-d908-0000-a99500f6e00e')
  IGNORE HYBRID TABLES;

Copy

Other CREATE DATABASE … CLONE commands, including those that use Time Travel with TIMESTAMP and OFFSET parameters, silently skip hybrid tables if any exist in the specified database. In other words, the behavior of these commands does not change.

Ref: 1792