Azure Load SF
Azure Blob Storage Load
The Azure Blob Storage Load component lets users load data into an existing table from objects stored in Azure Blob Storage.
This component is only available on Snowflake instances that are hosted on Microsoft Azure.
Important Information: External Stages and Metadata
If using an external stage, please be aware of the following information:
- All columns to be included in the load must be included in the Load Columns property, in the correct order and associated with the correct data type. The Create Table component can be used to specify the metadata of the columns.
- The Metadata Fields property will insert metadata columns at the end of the existing table and overwrite the same number of columns unless additional columns are added via the Create Table component..
- The table's data and structure are only accessed at runtime, meaning that additional columns must be added (and data types set) before the job is run. To ensure these columns are set up beforehand, users can load their data with Matillion ETL's Azure Blob Load Generator.
|Name||Text||A human-readable name for the component.|
|Stage||Select||Select a staging area for the data. Staging areas can be created through Snowflake using the CREATE STAGE command. Internal stages can be setup this way to store staged data within Snowflake.
Selecting [Custom] will avail the user of properties to specify a custom staging area on Azure Blob Storage
|Authentication||Select||Select the authentication method. Users can choose either:
Credentials: Uses Azure security credentials (configured in the Matillion ETL environment).
Storage Integration: use a Snowflake storage integration. A storage integration is a Snowflake object that stores a generated identity and access management (IAM) entity for your external cloud storage, along with an optional set of permitted or blocked storage locations (Amazon S3, Google Cloud Storage, or Microsoft Azure). More information can be found at CREATE STORAGE INTEGRATION.
|Storage Integration||Select||Select the storage integration. Storage integrations are required to permit Snowflake to read data from and write to a cloud storage location. Integrations must be set up in advance of selecting them in Matillion ETL. To learn more about setting up a storage integration, read Storage Integration Setup Guide.
Note: Storage integrations can be configured to support Amazon S3, Google Cloud Storage, or Microsoft Azure cloud storage regardless of the cloud provider that hosts your Snowflake account.
|Azure Storage Location||Text||The Azure storage location (including file path) for any data to be loaded.
When a user enters a forward slash character / after a folder name, a validation of the file path is triggered. This works in the same manner as the Go button.
|Pattern||Text||A string that will partially match all filenames that are to be included in the load. Defaults to '.*' indicating all files within the Azure Storage Location.|
|Warehouse||Select||Choose a Snowflake warehouse that will run the load. [Environment Default] will use the Warehouse defined in the environment.|
|Database||Select||Select the database that the newly-created table will belong to. [Environment Default] will use the Database defined in the environment.|
|Schema||Select||Select the table schema. The special value, [Environment Default] will use the schema defined in the environment. For more information on using multiple schemas, see this article.|
|Table||Select||Select an existing table to load data into.|
|Load Columns||Select Multiple||Choose the columns that will be loaded into the target table. Choosing no columns will result in all columns being loaded.|
|Format||Select||Select a pre-made file format that will automatically set many of the properties accordingly. These formats can be created through the Create File Format component.|
|File Type||Select||Select the expected file type that data will be loaded from. Supports AVRO, CSV, JSON, ORC, PARQUET and XML. Component properties will change to reflect the choice made here and give options based on the specific file type.|
|Compression||Select||Whether the input file is compressed in GZIP format, BROTLI, BZ2, DEFLATE, RAW_DEFLATE, ZSTD or not compressed at all.|
|Record Delimiter||String||(CSV only) Input a delimiter for records. This can be one or more single-byte or multibyte characters that separate records in an input file.
|Field Delimiter||Text||The delimiter that separates columns. The default is a Comma. A [TAB] character can be specified as "\t".|
|Skip Header||Integer||(CSV only) Specify the number of rows to skip. The default is 0.
If Skip Header is used, the value of the record delimiter will not be used to determine where the header line is. Instead, the specified number of CRLF will be skipped.
For example, if the value of Skip Header = 1, then Matillion ETL will skip to the first CRLF that it finds. If you have set the Field Delimiter property to be a single character without a CRLF, then Matillion ETL skips to the end of the file (treating the entire file as a header).
|Date Format||Text||Defaults to 'auto' - this can be used to manually specify a date format.|
|Time Format||Text||Defaults to 'auto' - this can be used to manually specify a time format.|
|Timestamp Format||Text||Defaults to 'auto' - this can be used to manually specify a timestamp format.|
|Escape||String||(CSV only) Specify a single character to be used as the escape character for field values that are enclosed. Default is NONE.|
|Escape Unenclosed Field||String||(CSV only) Specify a single character to be used as the escape character for unenclosed field values only. Default is \\.
If you have set a value in the property Field Optionally Enclosed, all fields will become enclosed, rendering the Escape Unenclosed Field property redundant, in which case it will be ignored.
|Trim Space||Select||Removes trailing and leading whitespace from the input data.|
|Field Optionally Enclosed||Text||A character that is used to enclose strings. Can be single quote (') or double quote (") or NONE (default). Note that the character chosen can be escaped by that same character.|
|Null If||String||Specify one or more strings (one string per row of the table) to convert to NULL values. When one of these strings is encountered in the file, it is replaced with a SQL NULL value for that field in the loaded table. Click + to add a string.|
|Error On Column Count Mismatch||Select||Generate an error if the number of delimited columns in the input does not match that of the table. If false, extra columns are not loaded into the table and missing columns are recorded as NULL in the table.|
|Empty Field As Null||Select||If this is set, empty columns in the input file will become NULL.|
|Encoding Type||Select||The type of encoding that has been applied to the data. This defaults to UTF-8.|
|Enable Octal||Select||(JSON File type) Enables parsing of octal numbers.|
|Allow Duplicates||Select||(JSON File type) Allows duplicate object field names (keeping only the last one used).|
|Strip Outer Array||Select||(JSON File type) Enable removal of outer square brackets from JSONs.|
|Strip Null Values||Select||(JSON File type) Enables removal of null values.|
|Ignore UTF8 Errors||Select||(JSON/XML File type) When true, replaces invalid UTF-8 sequences with the unicode replacement character (U+FFFD), instead of throwing an error.|
|Preserve Space||Select||(XML File Type) Leading and trailing spaces in elements are preserved if set to true.|
|Strip Outer Element||Select||(XML File Type) This will strip the outermost XML element, exposing the 2nd level elements as separate documents.|
|Disable Snowflake Data||Select||(XML File Type) Will disable recognition of Snowflake semi-structured data tags if set to true.|
|Disable Auto Convert||Select||(XML File Type) Enables conversion of numeric and Boolean values from text to their native types if set to true.|
|On Error||Select||Choose what to do when this component encounters an error.|
|Size Limit (B)||Text||The upper limit file size for any individual file loaded.|
|Purge Files||Select||Choose whether to destroy the source file after loading its data.|
|Truncate Columns||Select||If this is set, any instance of data in the input file that is too long to fit into the specified target column width will be truncated to fit instead of causing an error.|
|Force Load||Select||When TRUE, will load all files into Snowflake even if that file has not changed since a prior load. If FALSE (default), the component will attempt to avoid such redundant loads.|
|Metadata Fields||Column Selector||Snowflake metadata columns available to include in the load.
Snowflake automatically generates metadata for files in internal stages (i.e. Snowflake) and external stages (Microsoft Azure, Amazon S3, or Google Cloud Storage). This metadata is "stored" in virtual columns. These metadata columns are added to the staged data, but are only added to the table when included in a query of the table. For more information, read Querying Metadata for Staged Files.
This property is only available when an external stage is selected. To manage stages, click the Environments panel in the bottom-left, then right-click a Matillion ETL environment, and click Manage Stages. To learn more, read Manage Stages.