Rules and Guidelines for Directory-Level Partitioning
Rules and Guidelines for Directory-Level Partitioning
Consider the following rules and guidelines when you read from and write to a partition folder:
When you use access control lists, assign the required permissions to the partition folders.
When you import a directory that has a partition folder, the data type for the partition column is imported as a String.
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.
You cannot preview data for partition columns.
When you create target at the run time, you can add partition fields and arrange the partition columns in an order.
You cannot use the FileName port when you use directory-level partitioning. Ignore or delete the FileName port.
When you import a data object, the data and FileName port always show 0 as the partition order.
The partitioned directory that you select cannot have a partitioned column named FileName. The name is case insensitive.
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.