table) are maintained in the cloned objects. Tag associations in the source object (e.g. TagsĬloning a database or schema affects tags in that database or schema as follows: When a pipe is explicitly resumed, it only processes data files triggered as aĪ pipe clone in either state can be resumed by executing an ALTER PIPE … RESUME statement. Notifications as a result of newly staged files. In this state, pipes do not accumulate event When AUTO_INGEST = TRUE, a cloned pipe is set to the STOPPED_CLONED state. When AUTO_INGEST = FALSE, a cloned pipe is paused by default. The default state of a pipe clone is as follows: Stages internal (Snowflake) pipes are not cloned. Not clonedĬloning a database or schema does not clone objects of the following types in the database or schema:Ī database or schema clone includes only pipe objects that reference external (Amazon S3, Google Cloud Storage, or Microsoft Azure) Child objects inherit the name and structure of the source child objects at the time the statement is executed. A snapshot of the table data represents the state of the source data when the statement is executed or at the specified time/point Child objectsĪ database or schema clone includes all child objects active at the time the statement is executed or at the specified time/point Is executed, regardless of whether Time Travel is used. Inherits any other metadata, such as comments or table clustering keys, that is current in the source object at the time the statement Statement is executed or at a specified time/point in the past using Time Travel. The original table but does inherit any future grants defined for the object type in the schema (using theĪdditional Rules that Apply to Cloning Objects ¶ MetadataĪn object clone inherits the name and structure of the source object current at the time the CREATE CLONE If the COPY GRANTS keywords are not used, then the new object clone does not inherit any explicit access privileges granted on
Not inherit any future grants defined for the object type in the schema.
If the COPY GRANTS keywords are used, then the new object inherits any explicit access privileges granted on the original table but does The CREATE TABLE … CLONE syntax includes the COPY GRANTS keywords, which affect a new table Suspended – even if Automatic Clustering is not suspended for the source table. Were loaded into a source table can be loaded again into its clones.Īlthough a cloned table replicates the source table’s clustering keys, the new table starts with Automatic Clustering One consequence of this is that data files that STAGE FILE FORMAT) of the source table.Ī cloned table does not include the load history of the source table. Performed on the clone that modify existing data or add new data, such as:Īdding, deleting, or modifying rows in a cloned table.Ĭreating a new, populated table in a cloned schema.Ĭloning a table replicates the structure, data, and certain other properties (e.g. However, the following object types are not cloned:įor databases, schemas, and tables, a clone does not contribute to the overall data storage for the object until operations are In addition, to clone a schema or an object within a schema, your current role must have required privileges on the container object(s)įor databases and schemas, cloning is recursive:Ĭloning a database clones all the schemas and other objects in the database.Ĭloning a schema clones all the contained objects in the schema. To create a clone, your current role must have the following privilege(s) on the source object: Tables Parameters that are explicitly set on a source database, schema, or table are retained in any clones created from the source container or changes made to the source or clone are not reflected in the other object).
A clone is writable and is independent of its source (i.e.
0 kommentar(er)
