system.deployment.entity_deletion.method

The default entity deletion can be modified per runtime with an environment variable.

Can be set on environment level with CONFIG_ENVIRONMENT_VARIABLES.

See also:

• CONFIG_ENVIRONMENT_VARIABLES

• system.deployment.entity_deletion.method.{physical_type}

• Variables

Notes

Possible values are:

• DROP

  • The physical entity will be dropped from target database

• RENAME_AS_BACKUP

  • the physical entity will be renamed

• RENAME_AS_BACKUP_BY_RECREATE (For Snowflake Iceberg table)

  • Entity will be recreated with backup entity naming with the content of the original entity and the original entity will be dropped.

  • Use with ICEBERG_TABLE in case the deleted entity is wanted to be kept as backup

Behavior affects following physical entity types:

• TABLE

• DYNAMIC_TABLE

• ICEBERG_TABLE

By default:

• TABLE will use RENAME_AS_BACKUP

• DYNAMIC_TABLE will use DROP

• ICEBERG_TABLE will use DROP

All of the physical entity types can be set as DROP.

RENAME_AS_BACKUP can not be used for ICEBERG_TABLE as Iceberg table rename is not supported based on (Snowflake documentation for alter iceberg table), so therefore there is RENAME_AS_BACKUP_BY_RECREATE - option, which recreates the entire entity with the backed up name in to the new base location and removes the original entity.

Consider using physical type specific deletion method for ICEBERG_TABLE if DROP is not desired.

Examples

1. Entity deletion behavior when variable is set as RENAME_AS_BACKUP

   CODE

   ALTER TABLE <schema>.<entity> RENAME TO Z_<identifier>_BACKUP_<versionnumber>;

2. Entity deletion behavior when variable is set as DROP

   CODE

   DROP TABLE <schema>.<entity>;