OVERRIDE_FILE_LOAD
Target database: Snowflake, Amazon Redshift, Azure SQL Database, Azure Synapse SQL, Microsoft Fabric, Google BigQuery, Databricks
OVERRIDE_FILE_LOAD is a load step type that can be used to override an automatically generated file load. OVERRIDE_FILE_LOAD is available in file loads.
See also:
Usage
OVERRIDE_FILE_LOAD: sql_code
Variables
Variables supported in an OVERRIDE_FILE_LOAD step:
Variable | Description | Snowflake | Amazon Redshift | Azure SQL Database | Azure Synapse SQL | BigQuery |
---|---|---|---|---|---|---|
Resolved as the Snowflake copy options in file load execution. | x | |||||
Synonymous to storage_integration, resolved as the storage integration (Snowflake) or external data source (Azure SQL Database) in file load execution. | x | x | ||||
Resolved as the file format options in file load execution. | x | x | x | x | x | |
Resolved as the source file path in file load execution. | x | x | ||||
Resolved as a comma-separated source file list in file load execution. | x | x | ||||
Resolved as the source path(s) in file load execution. | x | x | x | x | ||
Resolved as the manifest-level run id in load execution. | x | x | x | x | x | |
Resolved as data source credentials in file load execution. | x | x | ||||
Resolved as encryption settings in file load execution. | x | |||||
Resolved as the storage integration (Snowflake) or as the external data source (Azure SQL Database) in file load execution. | x | x | x | |||
Resolved as a comma-separated list of target entity attributes in file load execution. | x | x | x | |||
Resolved as the target entity logical name in load execution. | x | x | x | x | x | |
Resolved as the target entity name in load execution. | x | x | x | x | x | |
Resolved as the schema of the target entity in load execution. | x | x | x | x | x |
Examples
See examples in Using Run ID Logic user guide. OVERRIDE_FILE_LOAD can be used with or without Run ID Logic.
See variable specific examples in the Variables documentation.