ALTER FUNCTION (Snowpark Container Services)¶

Syntax¶

ALTER FUNCTION [ IF EXISTS ] <name> ( [ <arg_data_type> , ... ] )
  RENAME TO <new_name>

ALTER FUNCTION [ IF EXISTS ] <name> ( [ <arg_data_type> , ... ] )
  SET CONTEXT_HEADERS = ( <context_function_1> [ , <context_function_2> ...] )

ALTER FUNCTION [ IF EXISTS ] <name> ( [ <arg_data_type> , ... ] )
  SET MAX_BATCH_ROWS = <integer>

ALTER FUNCTION [ IF EXISTS ] <name> ( [ <arg_data_type> , ... ] )
  SET COMMENT = '<string_literal>'

ALTER FUNCTION [ IF EXISTS ] <name> ( [ <arg_data_type> , ... ] )
  SET SERVICE = '<service_name>' ENDPOINT = '<endpoint_name>'

ALTER FUNCTION [ IF EXISTS ] <name> ( [ <arg_data_type> , ... ] )
  UNSET { CONTEXT_HEADERS | MAX_BATCH_ROWS | COMMENT }

Parameters¶

name

Specifies the identifier for the service function to alter. The identifier can contain the schema name and database name, as well as the function name. 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.

arg_data_type [ , ... ]

Specifies the arguments/input data types for the service function.

If the function accepts arguments, then the ALTER command must specify the argument types because functions support name overloading (that is, two functions in the same schema can have the same name), and the argument types are used to identify the function.

RENAME TO new_name

Specifies the new identifier for the service function; the combination of the identifier and existing argument data types must be unique for the schema.

For more information, see Identifier requirements.

Note

When specifying the new name for the service function, do not specify argument data types or parentheses; specify only the new name.

You can move the object to a different database and/or schema while optionally renaming the object. To do so, specify a qualified new_name value that includes the new database and/or schema name in the form db_name.schema_name.object_name or schema_name.object_name, respectively.

Note

• The destination database and/or schema must already exist. In addition, an object with the same name cannot already exist in the new location; otherwise, the statement returns an error.

• Moving an object to a managed access schema is prohibited unless the object owner (that is, the role that has the OWNERSHIP privilege on the object) also owns the target schema.

When an object is renamed, other objects that reference it must be updated with the new name.

SET ...

Specifies the properties to set for the function:

COMMENT = 'string_literal'

Specifies a comment for the function, which is displayed in the DESCRIPTION column in the SHOW FUNCTIONS and SHOW USER FUNCTIONS output.

SERVICE = '<service_name>' ENDPOINT = '<endpoint_name>'

Specifies the service name and the endpoint name as defined in the service specification.

CONTEXT_HEADERS = ( context_function_1 [ , context_function_2 ... ] )

It allows binding Snowflake context function results to HTTP headers.

Each value must be the name of a context function. Don’t include quote marks around the names.

More details about this parameter are in CREATE FUNCTION (Snowpark Container Services).

MAX_BATCH_ROWS = integer

Specifies the batch size when sending data to a service to increase concurrency

UNSET ...

Specifies the properties to unset for the function, which resets them to the defaults. Note that you can’t unset the service endpoint.

Access control requirements¶

A role used to execute this SQL command must have the following privileges at a minimum:

Note that operating on any object in a schema also requires the USAGE privilege on the parent database and schema.

For instructions on creating a custom role with a specified set of privileges, see Creating custom roles.

For general information about roles and privilege grants for performing SQL actions on securable objects, see Overview of Access Control.

Usage notes¶

• 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.

Examples¶

Rename a service function:

ALTER FUNCTION my_echo_udf(VARCHAR) RENAME TO my_echo_udf_temp;

Set a comment for a service function:

ALTER FUNCTION my_echo_udf(VARCHAR) SET COMMENT = 'some comment';

Set the maximum number of rows per batch for a service function:

ALTER FUNCTION my_echo_udf(number) SET MAX_BATCH_ROWS = 100;

Set the CURRENT_USER context header for a service function:

ALTER FUNCTION my_echo_udf(VARCHAR) SET CONTEXT_HEADER = (CURRENT_USER);

Unset MAX_BATCH_ROWS for a service function:

ALTER FUNCTION my_echo_udf(VARCHAR) UNSET MAX_BATCH_ROWS;