Microsoft Azure Blob Storage V3 Connector

Back Next

Rules and guidelines for mappings and mapping tasks

Consider the following rules and guidelines when you configure mappings and mapping tasks:

When you edit the metadata, all native data types change to Bigint and you cannot change the scale and precision of data types except for the string data type.

When you write a JSON file to Microsoft Azure Data Lake Blob Storage, ensure that the column names do not contain unicode characters.

Ensure that the scale of a double data type is not set to 0 in the target file when you read data from or write data to Microsoft Azure Blob Storage.

The data preview and mapping fail if you read an Avro file that contains binary fields.

Ensure that the field names in the source

or target

object do not contain special characters or unicode characters.

You cannot preview data when you read

or write

a compressed file.

When you write an Avro or a Parquet file, ensure that the file does not contain null values, else incorrect data in written in the target for the fields with null values.

You cannot select append blob as blob type when you read

or write a

JSON file.

Mappings for Microsoft Azure Blob Storage V3

Download Guide

Watch

Comments

Cloud Connectivity Homepage

Communities

Knowledge Base

Success Portal