UpdateSnowflakeDatabase 2025.3.28.13-SNAPSHOT¶

BUNDLE¶

com.snowflake.openflow.runtime | runtime-snowflake-processors-nar

DESCRIPTION¶

Updates the definition of a Snowflake table based on the schema provided in the incoming FlowFile. The schema is expected to bein JSON with the following format, regardless of whether it is provided via FlowFile content or specified as a property:{ “columns”: [ { “name”: “<column name>”, “type”: “<column type>”, “nullable”: <true/false>, “precision”: <precision, only for numeric type>, “scale”: <scale, only for numeric type> }, … ], “primaryKeys”: [“<name of first primary key column>”, “<name of second primary key column>”, …]}

TAGS¶

INPUT REQUIREMENT¶

REQUIRED

Supports Sensitive Dynamic Properties¶

false

PROPERTIES¶

Property	Description
Add Column Strategy	The strategy to use when the incoming schema has a column that is not present in the existing table
Add Not Null Strategy	The strategy to use when the incoming schema has a not-null constraint that is not present in the existing table
Column Name Transformation	An optional transformation that can be applied to the names of columns defined in the schema. This transformation is applied to the column names before they are compared to the existing columns in the table. This property can reference the following variables via Expression Language, in addition to attributes: `column.name`, `column.type`, `column.nullable`, `column.precision`, `column.scale`, `column.primaryKey`.
Column Removal Strategy	The strategy to use when the existing table has a column that is not present in the incoming schema
Connection Pool	The connection pool to use to connect to Snowflake
Create Stream	Whether or not to create a Snowflake Stream for the table
Creation Parameters	Additional parameters to include in the CREATE TABLE statement. For example, ‘CLUSTER BY (column_name)’
Desired Schema	The desired schema / table definition
Drop Column Strategy	The strategy to use when the existing table has a column that is not present in the incoming schema
Drop Not Null Strategy	The strategy to use when the existing table has a not-null constraint that is not present in the incoming schema
Include Not Null Constraints	Whether or not to include NOT NULL constraints in CREATE TABLE or ALTER TABLE ADD COLUMN statements
Include Primary Key Constraints	Whether or not to include primary key constraints in the creation statement
Modify Primary Key Strategy	The strategy to use when the incoming schema has a primary key that differs from the existing primary key. Modifying the Primary Key requires dropping the existing one, if any, and adding a new one.
Record Reader	Record Reader to use for obtaining the desired schema
Removed Column Name Suffix	The suffix to append to a column that was removed.For example, to rename column ‘foo’ to ‘foo__deleted’, the property can be set to `__deleted`
Schema Name	The name of the schema to update
Stream Creation Parameters	Additional parameters to include in the CREATE STREAM statement. For example, ‘APPEND_ONLY=TRUE’
Stream Name	The name of the stream to drop
Table Metadata Cache Expiration Time	The time in seconds after which the cache entry will be removed
Table Name	The name of the table to update
Table Schema Strategy	Specifies how to obtain the desired schema / table definition
Update Type	The type of update to perform
Use Table Metadata Cache	Whether to cache table’s metadata instead of reading it directly from Snowflake. Applies to [Create Table If Not Exists, Alter Table]

RELATIONSHIPS¶

NAME	DESCRIPTION
failure	The incoming FlowFile is routed to this relationship if the table cannot be updated
success	The incoming FlowFile is routed to this relationship after the table has been updated successfully