> ## Documentation Index > Fetch the complete documentation index at: https://docs.risingwave.com/llms.txt > Use this file to discover all available pages before exploring further. # Ingest data from Azure Blob > [Azure Blob Storage](https://learn.microsoft.com/en-us/azure/storage/blobs/), provided by Microsoft Azure, allows you to store and manage large amounts of unstructured data. Use the SQL statement below to connect RisingWave to Azure Blob Storage using Azblob connector. Note that the Azblob connector does not guarantee the sequential reading of files or complete file reading. ## Syntax ```sql theme={null} CREATE SOURCE [ IF NOT EXISTS ] source_name schema_definition [INCLUDE { file | offset | payload } [AS ]] WITH ( connector = 'azblob', connector_parameter = 'value', ... ) FORMAT data_format ENCODE data_encode ( without_header = 'true' | 'false', delimiter = 'delimiter' ); ``` **schema\_definition**: ```sql theme={null} ( column_name data_type [ PRIMARY KEY ], ... [ PRIMARY KEY ( column_name, ... ) ] ) ``` ### Connector parameters | Field | Notes | | :------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | azblob.container\_name | **Required**. The name of the container the data source is stored in. | | azblob.credentials.account\_name | **Optional**. The name of the Azure Blob Storage account. | | azblob.credentials.account\_key | **Optional**. The account key for the Azure Blob Storage account. | | azblob.endpoint\_url | **Required**. The URL of the Azure Blob Storage service endpoint. | | match\_pattern | **Conditional**. Set to find object keys in `azblob.container_name` that match the given pattern. Standard Unix-style [glob](https://en.wikipedia.org/wiki/Glob%5F%28programming%29) syntax is supported. A typical usage follows the `prefix/*.suffix` pattern. For example, `your_directory/*.parquet` matches all Parquet files under `your_directory/`. If `match_pattern` does not contain `/`, the scan runs from the container root. | | compression\_format | **Optional**. Specifies the compression format of the file being read. When set to gzip or gz, the file reader reads all files with the `.gz` suffix; when set to `None` or not defined, the file reader will automatically read and decompress `.gz` and `.gzip` files. | ### Other parameters | Field | Notes | | :---------------- | :----------------------------------------------------------------------------------------------------------------------------------------- | | *data\_format* | Supported data format: PLAIN. | | *data\_encode* | Supported data encodes: CSV, JSON, PARQUET. | | *without\_header* | This field is only for CSV encode, and it indicates whether the first line is header. Accepted values: `true`, `false`. Default is `true`. | | *delimiter* | How RisingWave splits contents. For JSON encode, the delimiter is `\n`; for CSV encode, the delimiter can be one of `,`, `;`, `E'\t'`. | ### Additional columns | Field | Notes | | :------- | :------------------------------------------------------------------------------------------------------------------------------ | | *file* | **Optional**. The column contains the file name where current record comes from. | | *offset* | **Optional**. The column contains the corresponding bytes offset (record offset for parquet files) where current message begins | ## Read Parquet files from Azure Blob Added in v2.3.0. You can use the table function `file_scan()` to read Parquet files from Azure Blob, either a single file or a directory of Parquet files. ```sql Function signature theme={null} file_scan ('parquet', 'azblob', endpoint, account_name, account_key, file_location) ``` When reading a directory of Parquet files, the schema will be based on the first Parquet file listed. Please ensure that all Parquet files in the directory have the same schema. ## Examples Here are examples of connecting RisingWave to the Azblob source to read data from individual streams. ```sql theme={null} CREATE SOURCE s( id int, name varchar, age int ) WITH ( connector = 'azblob', azblob.container_name = 'xxx', azblob.credentials.account_name = 'xxx', azblob.credentials.account_key = 'xxx', azblob.endpoint_url = 'xxx', ) FORMAT PLAIN ENCODE CSV ( without_header = 'true', delimiter = ',' -- set delimiter = E'\t' for tab-separated files ); ``` ```sql theme={null} CREATE SOURCE s1( id int, name TEXT, age int, mark int, ) WITH ( connector = 'azblob', azblob.container_name = 'xxx', azblob.credentials.account_name = 'xxx', azblob.credentials.account_key = 'xxx', azblob.endpoint_url = 'xxx', match_pattern = '%Ring%*.ndjson', ) FORMAT PLAIN ENCODE JSON; ``` Use the `payload` keyword to ingest JSON data when you are unsure of the exact schema beforehand. Instead of defining specific column names and types at the very beginning, you can load all JSON data first and then prune and filter the data during runtime. Check the example below: ```sql theme={null} CREATE TABLE table_include_payload (v1 int, v2 varchar) INCLUDE payload WITH ( connector = 'azblob', topic = 'azblob_1_partition_topic', properties.bootstrap.server = 'message_queue:29092', scan.startup.mode = 'earliest' ) FORMAT PLAIN ENCODE JSON; ``` ```sql theme={null} CREATE SOURCE s2( id int, name varchar, age int ) WITH ( connector = 'azblob', azblob.container_name = 'xxx', azblob.credentials.account_name = 'xxx', azblob.credentials.account_key = 'xxx', azblob.endpoint_url = 'xxx', match_pattern = '*.parquet', ) FORMAT PLAIN ENCODE PARQUET; ```