Skip to content

Step 1: Configure a Landing Zone entity

A Landing Zone entity is the initial stage for ingesting and storing raw data in your data platform. It provides a secure, scalable staging area for large volumes of unprocessed data, preserving the original format for downstream processing.

Landing Zone entities validate incoming data and resource types, ensuring data integrity before moving to the Bronze, Silver, or Gold layers. For example, if your source system contains 10 tables, create 10 Landing Zone entities—one for each table.

Privacy entities use Parquet

If a Landing Zone entity includes columns that require encryption, anonymization, or pseudonymization, the data is always stored as a Parquet file, regardless of the original format.

To configure a Landing Zone entity, provide the following details:

Source configuration

  • Pipeline: Obsolete, can be ignored.
  • Data source: Select the appropriate data source.
  • Source schema: Enter the schema name where the data resides.
  • Source name: Enter the table or file name to extract.

Load settings

  • Incremental: Choose whether to extract data incrementally. Learn more about incremental extraction.
  • Privacy entity: Indicate if the data contains sensitive columns. Learn how to add encryption.
  • If enabled, you are able to specify which columns require encryption:
    • Name: Enter the column name
    • Privacy Option: Select the privacy option for the column (more options may be added in the future).
    • Foreign Keys: Indicate if this column is a foreign key. This allows the foreign key to still work when the column is encrypted. If this option is enabled, the column will be hashed in addition to being encrypted (Only available for Encryption v2).
  • Entity values: Adds additional parameters for extraction. These are often optional, but when they are required for certain scenarios, the portal will add them by default and must be specified.

Note

To see the complete list of entity values applicable for the landing zone entities click here.

Tip

Use Edit in advanced mode to add entity values in JSON format. This is recommended when you need to pass objects as values(for example CustomParametersJSON), because the advanced editor includes JSON validation.

Target configuration

  • Lakehouse: Select the lakehouse where your data will be stored.
  • File path: Automatically generated path for storing your data.
  • File name: Automatically generated name for the extracted data file(s).
  • File type: Select the original data format. For tables, select Parquet.

Privacy entities use Parquet

If a Landing Zone entity includes columns that require encryption, anonymization, or pseudonymization, the data is always stored as a Parquet file, regardless of the original format.
Enabling this option may increase processing time.

Next steps