Managing and configuring the Winning Variant Snowflake Native App
admin
application role to execute any of the examples described on this page.
admin
application role is granted the following permissions: OPERATE
, MODIFY
, USAGE
, MONITOR
. This means that an admin
can alter the compute pool directly.
management
schema):
Procedure | Description |
---|---|
suspend_services() | Suspends all services. |
suspend_config_service() | Suspends just the configuration service. |
suspend_variant_service() | Suspends just the variant service. |
resume_services() | Resumes all services. |
resume_config_service() | Resumes the configuration service. |
resume_variant_service() | Resumes the variant service. |
get_service_status() | Gets the status of all services. |
get_service_endpoints() | Shows ingress URLs for all services. |
Property | Description | Default |
---|---|---|
VARIANTAPI:CONFIG_REFRESH_SECONDS | How often (in seconds) to refresh the configuration in the Variant API from the underlying tables. The Variant API must be restarted for this to take effect. Variant API instances are automatically updated with new configuration in real-time, however this exists as a safety fallback to ensure that configuration is fresh. | 21600 (6 hours) |
VARIANTAPI:CSV_ROTATE_SECONDS | How often (in seconds) for the assignment CSV cache to be rotated. | 1800 (30 minutes) |
100
should be stored as '100'
.SELECT
from management.config_properties
.
Example