Lists the application objects for which you have access privileges across your entire account in the Snowflake Native App Framework.
The output returns metadata and properties for the application object, ordered lexicographically by name. This is important to note if you wish to filter the results using the provided filters.
Syntax¶SHOW APPLICATIONS [ LIKE '<pattern>' ] [ STARTS WITH '<name_string>' ] [ LIMIT <rows> [ FROM '<name_string>' ] ];
Copy
Parameters¶LIKE 'pattern'
Optionally filters the command output by object name. The filter uses case-insensitive pattern matching, with support for SQL wildcard characters (% and _).
For example, the following patterns return the same results:
... LIKE '%testing%' ...
... LIKE '%TESTING%' ...
. Default: No value (no filtering is applied to the output).
STARTS WITH 'name_string'
Optionally filters the command output based on the characters that appear at the beginning of the object name. The string must be enclosed in single quotes and is case sensitive.
For example, the following strings return different results:
... STARTS WITH 'B' ...
... STARTS WITH 'b' ...
. Default: No value (no filtering is applied to the output)
LIMIT rows [ FROM 'name_string' ]
Optionally limits the maximum number of rows returned, while also enabling “pagination” of the results. The actual number of rows returned might be less than the specified limit. For example, the number of existing objects is less than the specified limit.
The optional FROM 'name_string' subclause effectively serves as a “cursor” for the results. This enables fetching the specified number of rows following the first row whose object name matches the specified string:
The string must be enclosed in single quotes and is case sensitive.
The string does not have to include the full object name; partial names are supported.
Default: No value (no limit is applied to the output)
Note
For SHOW commands that support both the FROM 'name_string' and STARTS WITH 'name_string' clauses, you can combine both of these clauses in the same statement. However, both conditions must be met or they cancel out each other and no results are returned.
In addition, objects are returned in lexicographic order by name, so FROM 'name_string' only returns rows with a higher lexicographic value than the rows returned by STARTS WITH 'name_string'.
For example:
... STARTS WITH 'A' LIMIT ... FROM 'B' would return no results.
... STARTS WITH 'B' LIMIT ... FROM 'A' would return no results.
... STARTS WITH 'A' LIMIT ... FROM 'AB' would return results (if any rows match the input strings).
The command output provides application object properties and metadata in the following columns:
Column
Description
created_on
Date and time when the application object was created.
name
The name of the application object.
is_default
Specifies if the application object is in the default namespace for the user.
is_current
Specifies if the application object is in the current session context.
source_type
Specifies the source of the application object. Valid values are:
APPLICATION PACKAGE
LISTING
source
The name of the application package or listing used to create the application object.
owner
The role used to create the application object.
comment
Text that provides information about the application object.
version
The version identifier used to create the application object.
label
The version label of the application object. This label is visible to consumer when they install a Snowflake Native App.
patch
The patch number used to create the application object.
options
For an application object, this field is always empty.
retention_time
The retention time of the application object.
upgrade_state
The current state of the background installation or upgrade of the application object. Valid values are:
INSTALLING: The application object is in the process of being created.
INSTALL_FAILED: The creation of the application object failed. The application object remains in the INSTALL_FAILED state until it is dropped. See the UPGRADE_FAILURE_REASON column of the DESCRIBE APPLICATION command for information about why the installation or upgrade failed.
COMPLETE: The setup script successfully completed and the application object was created or upgraded.
QUEUED: The application object is queued for upgrade.
UPGRADING: The application object is in the process of being upgraded.
FAILED: All upgrade attempts failed. The reason for the failure is listed in the UPGRADE_FAILURE_REASON column, if present. The instance remains in the FAILED state until a release directive is updated to point to a different version than the one that the upgrade was targeting, as defined in the TARGET_UPGRADE_VERSION column.
QUEUED_RETRY: The instance failed one or more upgrade attempts. The reason for the failure is indicated in UPGRADE_FAILURE_REASON: The instance is queued to perform another upgrade attempt.
DISABLED: The application object and its upgrades were disabled. In this state the instance will be inaccessible for consumers, it will not be considered for upgrades and will not block application package version drop. The reason for the failure is listed in the UPGRADE_FAILURE_REASON column, if present.
The command doesn’t require a running warehouse to execute.
The command only returns objects for which the current user’s current role has been granted at least one access privilege.
The MANAGE GRANTS access privilege implicitly allows its holder to see every object in the account. By default, only the account administrator (users with the ACCOUNTADMIN role) and security administrator (users with the SECURITYADMIN role) have the MANAGE GRANTS privilege.
To post-process the output of this command, you can use the pipe operator (->>) or the RESULT_SCAN function. Both constructs treat the output as a result set that you can query.
The output column names for this command are generated in lowercase. If you consume a result set from this command with the pipe operator or the RESULT_SCAN function, use double-quoted identifiers for the column names in the query to ensure that they match the column names in the output that was scanned. For example, if the name of an output column is type, then specify "type" for the identifier.
+-------------------------------+------------------------+------------+------------+---------------------+----------------------------+---------------+---------+---------------------+-----------------+-------+---------+----------------+ | created_on | name | is_default | is_current | source_type | source | owner | comment | version | label | patch | options | retention_time | |-------------------------------+------------------------+------------+------------+---------------------+----------------------------+---------------+---------+---------------------+-----------------+-------+---------+----------------| | 2023-02-03 10:14:09.828 -0800 | hello_snowflake_app | N | Y | APPLICATION PACKAGE | hello_snowflake_package | PROVIDER_ROLE | | v1 | Version v1 | 0 | | 1 | | 2023-03-22 16:12:40.373 -0700 | PRODUCTION_APP | Y | Y | APPLICATION PACKAGE | hello_snowflake_package | PROVIDER_ROLE | | v2 | Version v2 | 0 | | 1 | +-------------------------------+------------------------+------------+------------+---------------------+----------------------------+---------------+---------+---------------------+-----------------+-------+---------+----------------+
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4