Azure Blob Storage Connector

The Azure Blob Storage Connector, known by the type name blob, exposes stored procedures to leverage resources stored in Azure Blob Storage.

Connector-specific Connection Properties

Property name	Description
`accountName`	Azure account name
`accountKey`	Azure account key
`sasToken`	SAS token
`defaultEndpointsProtocol`	Default endpoint protocol
`containerName`	Name of the Azure container
`prefix`	The `pathAndPattern` prefix to be used when handling files

sasToken and accountKey are mutually exclusive: either a SAS Token or an Account Key must be specified.

Examples

1. Connecting using an Account Key:

SQL

CALL SYSADMIN.createConnection(name => 'blob', jbossCLITemplateName => 'blob', connectionOrResourceAdapterProperties => 'accountName=<accountName>,accountKey=<accountKey>,defaultEndpointsProtocol=https,containerName=<container name>');;
CALL SYSADMIN.createDataSource(name => 'blob', translator => 'ufile', modelProperties => 'importer.useFullSchemaName=false', translatorProperties => '');;

2. Connecting using a SAS Token:

Example

SQL

CALL SYSADMIN.createConnection(name => 'blob', jbossCLITemplateName => 'blob', connectionOrResourceAdapterProperties => 'accountName=<accountName>,sasToken=<sasToken>,defaultEndpointsProtocol=https,containerName=<container name>');;
CALL SYSADMIN.createDataSource(name => 'blob', translator => 'ufile', modelProperties => 'importer.useFullSchemaName=false', translatorProperties => '');;

Prefix

The prefix allows to limit the result set.

The 'Prefix' property value gets passed in connectionOrResourceAdapterProperties;
All procedures of the connector automatically take the prefix into consideration: e.g., calling listFiles(pathAndPattern => NULL) still applies the prefix from the data source settings;
If the data source has a prefix configured, and a pathAndPattern gets passed, the values get concatenated. For example, if a data source is configured with prefix a/b, and listFiles(pathAndPattern => 'c/d') gets called, this results in a/b/c/d.