You must import a directory that contains only partition folders and select the source type as

Directory

in the advanced source property.

If you import a partition directory that does not have data, a validation error is encountered.

If you import a partition directory that has a partition folder but no files in the partition folder, a validation error is encountered.

The FileName field has 0 as the partition order.

The partitioned directory that you select cannot have a partitioned column named FileName. The name is case insensitive.

When you import an existing target object or create a new target object with a partition directory, the FileName field is not added on the target side. The FileName field is only present at the source side.

When you pass a timestamp value in a partition column, the value gets encoded. For example, 03:26:01 is encoded as 03%3A26%3A01.

When you pass a special character in a partition column, the value gets encoded. For example, #" is encoded as %23%22

When you import a directory that has a partition folder, the data type for the partition column is imported as a String.

You cannot write hierarchical data types to a partitioned file.

You cannot edit the data type for a partition column.

You cannot use the

Edit Metadata

option with partition columns.

You cannot use the

View Schema

option for a partition directory at source and target side.

You cannot use the

Import from Schema File

option for partition directory at source because the schema file does not have information for partition columns.

You cannot use the

Data Preview

option with partition columns.

You cannot select the partition columns in a mapping task if the target object is parameterized.

For

Create Target

, you can add partition fields and arrange the partition columns in an order.

When you write data types other than numeric, date, timestamp, and string to a partitioned file, you must set the following spark custom property in the mapping task to false:

spark.sql.sources.partitionColumnTypeInference.enabled

When you import a Microsoft Azure Data Lake Storage Gen2 object that has partition columns, the partition fields are listed at the end of the list.

If a partition column contains data that has more than 255 characters, the data is truncated and only 255 characters are written in the partition column.

If a partition column name contains more than 74 characters, the name is truncated and only 74 characters are written in the partition column name.

The value of the partition directory file path formed using the combination of the partition column name and the target file within the partition directory must not exceed 1024 characters. Otherwise, the mapping will fail.

You cannot use the

File Name Override

option with partition columns.

When you read or write JSON files, you cannot use the

Data elements to sample

and

Memory available to process data

advanced properties with partition columns.