Modifies the properties for an existing notification integration for sending a message to a Google Pub/Sub topic.
CREATE NOTIFICATION INTEGRATION (outbound to a Google Pub/Sub topic) , DESCRIBE NOTIFICATION INTEGRATION , DROP INTEGRATION , SHOW NOTIFICATION INTEGRATIONS
ALTER [ NOTIFICATION ] INTEGRATION [ IF EXISTS ] <name> SET
[ ENABLED = { TRUE | FALSE } ]
GCP_PUBSUB_SUBSCRIPTION_NAME = '<subscription_id>'
[ COMMENT = '<string_literal>' ]
ALTER [ NOTIFICATION ] INTEGRATION <name> SET TAG <tag_name> = '<tag_value>' [ , <tag_name> = '<tag_value>' ... ]
ALTER [ NOTIFICATION ] INTEGRATION <name> UNSET TAG <tag_name> [ , <tag_name> ... ]
ALTER [ NOTIFICATION ] INTEGRATION [ IF EXISTS ] <name> UNSET COMMENT
Copy
Parameters¶name
Specifies the identifier for the integration to alter.
If the identifier contains spaces or special characters, the entire string must be enclosed in double quotes. Identifiers enclosed in double quotes are also case-sensitive.
For more information, see Identifier requirements.
SET ...
Specifies one or more properties/parameters to set for the integration (separated by blank spaces, commas, or new lines):
ENABLED = { TRUE | FALSE }
Specifies whether to initiate operation of the integration or suspend it.
TRUE enables the integration.
FALSE disables the integration for maintenance. Any integration between Snowflake and a third-party service fails to work.
GCP_PUBSUB_TOPIC_NAME = 'topic_id'
Identification of the Pub/Sub topic to which Snowflake pushes notifications.
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 information about specifying tags in a statement, see Tag quota for objects.
COMMENT = 'string_literal'
String (literal) that specifies a comment for the integration.
Default: No value
UNSET ...
Specifies one or more properties/parameters to unset for the integration, which resets them back to their defaults:
TAG tag_name [ , tag_name ... ]
COMMENT
Regarding metadata:
Attention
Customers should ensure that no personal data (other than for a User object), sensitive data, export-controlled data, or other regulated data is entered as metadata when using the Snowflake service. For more information, see Metadata fields in Snowflake.
Disabling or dropping an integration might not take effect immediately because the integration might be cached. To expedite the removal process, remove the integration privilege from the cloud provider.
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