Partitioning files-based datasets¶
All datasets that are based on files can be partitioned. This includes the following kinds of datasets :
- Server Filesystem
- Hadoop HDFS
- Amazon S3
- Remote files
On files-based datasets, partitioning is defined by the layout of the files on disk.
Partitioning a files-based dataset cannot be defined by the content of a column within this dataset
For example, if a filesystem is organized this way:
This folder can be partitioned at the day level, with one folder per partition.
Files-based partitioning is defined by a matching pattern which allows mapping each file to a given partition identifier.
For example, the previous example would be represented by the pattern
Define a partitioned dataset¶
You first need to have defined the connection and format params. Once this is OK and you can see your data, go to the Partitioning tab, and click “Activate partitioning”
Dataiku DSS automatically tries to recognize the pattern. If it succeeds, a partitioning scheme will be suggested, which you can directly use.
To manually define partitioning, first, add your dimensions.
- You can add a single “time” dimension. Time dimension have a fixed granularity, which can be year, month, day or hour.
- You can add multiple discrete value dimensions
Each dimension has a name.
Then, define the pattern. The indicators on the right of the pattern allow you to check that you have used all dimensions in the pattern.
The time dimension is referred in the pattern by the
%Y (year, on 4 digits),
%M (month, on 2 digits),
%D (day, on 2 digits) and
%H (hour, on 2 digits) specifiers.
Each discrete value dimension is referred by the
The above example defines a partitioning scheme with two dimensions, which would match files:
Your file names and paths must exactly match the pattern.
'/' is important, as all paths are anchored to the root of the dataset.
.* is important : it catches all files with the given prefix.
The “Test” button inspects the dataset and displays which partitions would be generated by the current pattern.
If 0 partitions are detected, it generally means that your pattern does not match your files.
More information might be available in the backend log file. See Diagnosing and debugging issues for more information.