Deploying builds a table in the Lake with its current column configuration. Until a table is deployed, parts of its popup stay locked. This page covers deploying from the table popup and the changes that drop and recreate a deployed table.
One banner shows at a time: a deploy error comes first, then the primary-key notice, then the ready notice. The popup deploys this table only; to deploy several tables together, see Deploy tables.
A table needs at least one primary key column to deploy. Without one, the banner reads Primary key required. Define a primary key column before this table can be deployed. and offers Go to Columns:
The key check comes first: while the table has no key, the popup asks for one even when the table is otherwise ready to deploy. Set up a table's columns covers the PK flag and its rules.
Until a table is deployed, its Settings tab shows Table Not Deployed with Deploy this table to access settings. Deployment creates the table in the lake with your current column configuration. The Lake mode of Preview stays unavailable with the tooltip Deploy the table to preview lake data, and Refresh stays disabled.
If the table also has no primary key, the tab shows Primary Key Required with This table must have at least one primary key column before it can be deployed. Define a primary key in the Columns tab to continue. instead.
Deploy the table and the locked parts open; see Preview table data and Run, stop and troubleshoot loads.
A failed deploy shows an error banner above the form. The whole banner is clickable, and it offers:
The notification uses the first failed reason, or Failed to deploy table when the server gives none. For the messages and their fixes, see Lake troubleshooting.
Some changes to a deployed table cannot be applied in place. The table is dropped and recreated, and its existing data is permanently lost. Each of these changes asks for confirmation first:
| You change | The dialog | What it warns |
|---|---|---|
| The sync type to one in another DDL family | Change DDL Type from {old} to {new}? | This will drop and recreate the table. All existing data will be permanently lost. |
| The Date Column of an incremental table | Change Date Column? | The same data-loss warning. |
| A primary key or partition column's definition: key status, data type or data domain | Primary Key Change Detected | The dialog warns that the change drops and recreates the table and all existing data will be permanently lost, then asks Do you want to proceed? |
A sync type change inside the same DDL family still confirms with Change sync type from {old} to {new}?, without the data-loss warning; the change applies after you confirm. A table that is not deployed yet changes sync type with no confirmation. See Choose a sync type for the families, and Configure a table for what a sync type change updates.
A drop and recreate cannot be undone, and the table holds no data until its next load. Run the table again after the change; see Run, stop and troubleshoot loads.
Deploying needs Add/Modify Lake Objects, like saving the table's settings. See Who can do what in the Lake.
Open the table, then click Deploy in the banner that reads This table is ready to deploy. When the deploy finishes, the Settings tab and the Lake preview open. The popup builds this table only; to deploy several tables from the tree, see Deploy tables.
A table cannot be deployed without at least one primary key column. The banner reads Primary key required. Define a primary key column before this table can be deployed. Click Go to Columns, tick PK on the column that identifies each row, and click Apply. See Set up a table's columns.
The table has not been deployed yet. The tab opens once it is: Deploy this table to access settings. Deployment creates the table in the lake with your current column configuration. The Lake mode of Preview and Refresh unlock with it.
Moving to a sync type in another DDL family, for example from Full Reload (Truncate Insert) to Full Reload (Upsert), drops and recreates the table after you confirm Change DDL Type from {old} to {new}?. The dialog warns that all existing data will be permanently lost. A change inside the same family confirms without the warning.
The confirmation appears on a deployed table that already has a date column. Changing the Date Column drops and recreates the table, so the popup asks Change Date Column? and warns that all existing data will be permanently lost. After the change, the table loads fresh data on its next run.
On a deployed table, the dialog appears when a column's PK or partition status changes, or when a column that is a primary key or partition column changes its data type or data domain. It warns that the definition change drops and recreates the table, and asks whether to proceed; cancel the dialog to keep the table as it is.
The error banner above the form holds the message; click it or View details to read the full error. Redeploy retries this table. If the server gave no reason, the notification reads Failed to deploy table. For the messages and their fixes, see Lake troubleshooting.
The previous data is gone; the table holds nothing until its next load. Run the table again from the Settings tab, or let its workflow run. What the next run reads depends on the sync type. See Run, stop and troubleshoot loads and Choose a sync type.