ALTER APPLICATION PACKAGE¶

Syntax¶

ALTER APPLICATION PACKAGE [ IF EXISTS ] <name> SET
  [ DATA_RETENTION_TIME_IN_DAYS = <integer> ]
  [ MAX_DATA_EXTENSION_TIME_IN_DAYS = <integer> ]
  [ DEFAULT_DDL_COLLATION = '<collation_specification>' ]
  [ COMMENT = <string-literal> ]
  [ DISTRIBUTION = { INTERNAL | EXTERNAL } ]

ALTER APPLICATION PACKAGE [ IF EXISTS ] <name> UNSET
  [ DATA_RETENTION_TIME_IN_DAYS ]
  [ MAX_DATA_EXTENSION_TIME_IN_DAYS ]
  [ DEFAULT_DDL_COLLATION ]
  [ COMMENT ]
  [ DISTRIBUTION ]

ALTER APPLICATION <name> SET TAG <tag_name> = '<tag_value>' [ , <tag_name> = '<tag_value>' ... ]

ALTER APPLICATION <name> UNSET TAG <tag_name> [ , <tag_name> ... ]

Parameters¶

name

Specifies the identifier for the application package to alter. If the identifier contains spaces, special characters, or mixed-case characters, the entire string must be enclosed in double quotes. Identifiers enclosed in double quotes are also case-sensitive.

SET

Specifies one (or more) properties to set for the application package (separated by blank spaces, commas, or new lines). For more details about the properties you can set, see CREATE APPLICATION.

TAG tag_name = 'tag_value' [ , tag_name = 'tag_value' , ... ]

Specifies the tag name and the tag string value.

The tag value is always a string, and the maximum number of characters for the tag value is 256.

For details about specifying tags in a statement, refer to Tag quotas for objects and columns.

UNSET

Specifies one (or more) properties and/or session parameters to unset for the application package, which resets them to the defaults.

For details about each property, refer to CREATE APPLICATION PACKAGE

TAG tag_name [ , tag_name ... ]

Removes the specified tag from the application package.

Usage Notes¶

• If you do not specify the values for the optional properties, the command uses the values specified in the application manifest file.

  If you specify values for the properties in the command and in the application manifest file, the values specified in the command take precedence.

• If two versions are active (e.g. if the current version has not finished rolling out), adding a new version results in an error.

• New versions are added with a default patch number of 0.

Examples¶

ALTER APPLICATION PACKAGE hello_snowflake_package
  ADD VERSION v1_1
  USING '@hello_snowflake_code.core.hello_snowflake_stage';

+---------------------------------------------------------------------------------------+---------+-------+
| status                                                                                | version | patch |
|---------------------------------------------------------------------------------------+---------+-------|
| Version 'v1_1' of application package 'hello_snowflake_package' created successfully. | v1_1    |     0 |
+---------------------------------------------------------------------------------------+---------+-------+