Navigation

Supported Partition Attribute TypesΒΆ

Beta

The Atlas Data Lake is available as a Beta feature. The product and the corresponding documentation may change at any time during the Beta stage. For support, see Atlas Support.

The following table lists the supported data types for partition attributes in the path and an example path for each data type:

Key Data Type Example
string Parses the filename as a string. This is the default data type. If a data type is not specified for a partition attribute, Data Lake interprets the partition attribute as a string.

filename: /employees/949-555-0195.json

path: /employees/{phone string}

OR

path: employees/{phone}

In the above path examples, phone is interpreted as a string.

int Parses the filename as an integer.

filename: /zipcodes/90210.json

path: /zipcodes/{zipcode int}

In the above example, zipcode is interpreted as an integer.

isodate Parses the filename as an ISO 8601 format date

filename: /metrics/2019-01-03T00:00:00Z.json

path: /metrics/{startTimestamp isodate}

In the above example, startTimestamp is interpreted as an ISODate.

epoch_secs Parses the filename as a Unix timestamp in seconds.

filename: /metrics/1549046112.json

path: /metrics/{startTimestamp epoch_secs}

In the above example, startTimestamp is interpreted as a Unix timestamp in seconds.

epoch_millis Parses the filename as a Unix timestamp in milliseconds.

filename: /metrics/1549046112000.json

path: /metrics/{startTimestamp epoch_millis}

In the above example, startTimestamp is interpreted as a Unix timestamp in milliseconds.

objectid Parses the filename as an ObjectId.

filename: /metrics/507f1f77bcf86cd799439011.json

path: /metrics/{objid objectid}

In the above example, objid is interpreted as an ObjectId.

uuid Parses the filename as a UUID of binary subtype 4.

filename: /metrics/3b241101-e2bb-4255-8caf-4136c566a962.json

path: /metrics/{myUuid uuid}

In the above example, myUuid is interpreted as a UUID of binary subtype 4.