Skip to main content
The Zero Copy Clone test component creates a clone of a specified Snowflake object using Snowflake’s zero-copy cloning feature. A zero-copy clone creates an instant copy of a source object without duplicating the underlying data. Additional storage is only consumed if the cloned object is modified.
This component is only available in Tests.

​
Properties

​
string
required
A human-readable name for the component.
​
drop-down
required
The type of Snowflake object to clone. Supports Schema and Table.
​
drop-down
required
The Snowflake database that contains the object to clone. The special value [Environment Default] uses the database defined in the environment. Read Database, Schema, and Share DDL to learn more.
​
drop-down
required
The Snowflake schema to clone. The special value [Environment Default] uses the schema defined in the environment. Read Database, Schema, and Share DDL to learn more.
​
drop-down
required
The Snowflake table to clone.Available when Clone object type is set to Table.
​
drop-down
required
The Snowflake database where the cloned object will be created. The special value [Environment Default] uses the database defined in the environment. Read Database, Schema, and Share DDL to learn more.
​
string
required
The name of the new cloned schema.Available when Clone object type is set to Schema.
​
drop-down
required
The Snowflake schema where the cloned object will be created. The special value [Environment Default] uses the schema defined in the environment. Read Database, Schema, and Share DDL to learn more.Available when Clone object type is set to Table.
​
string
required
The name for the new cloned table.Available when Clone object type is set to Table.
​
drop-down
required
Choose how to create a target object.Select one of the following options:
  • Create: This is the default option. It creates a new schema, and will cause an error if a schema with the same name already exists. Existing data will not be affected.
  • Create If Not Exists: This option creates a new schema when a schema of the same name does not already exist. This option will not destroy existing data.
  • Replace: If a schema with the name you specify in the Target schema name property already exists, the existing schema is replaced by a new schema when the pipeline finishes. Any data from the existing schema (to be replaced) will be lost.