← All updates Databricks Update One-Pager Light version
databricks Platform · Updated Jul 24, 2025

Lakeflow Pipelines

Moving tables between Spark Declarative Pipelines is now generally available.

What it does

This update allows users to move streaming tables and materialized views between Spark Declarative Pipelines in Lakeflow, enabling the destination pipeline to manage the table instead of the source. It supports various scenarios such as splitting large pipelines, merging multiple pipelines, and changing refresh frequencies. The feature requires specific Databricks Runtime versions and shared metastores between workspaces for cross-workspace moves.

Why it matters

This capability enhances flexibility in data pipeline management, allowing organizations to optimize their ETL processes by reorganizing tables without the need for extensive rewrites. It can lead to improved performance, reduced operational complexity, and better resource utilization, ultimately driving productivity and cost efficiency.

Key capabilities
Move Tables Between Pipelines
Users can transfer tables from one pipeline to another, allowing for better organization and management.
Support for Multiple Scenarios
Facilitates splitting, merging, and adjusting refresh frequencies of pipelines.
Cross-Workspace Table Movement
Enables moving tables across different workspaces that share a metastore.
Default Publishing Mode Requirement
The destination pipeline must use the default publishing mode for successful table transfers.
Prerequisites
Databricks Runtime 16.3 or above for ALTER command; 17.2 for cross-workspace moves.
Both pipelines must share a metastore.
User must be the owner of both source and destination pipelines.
Recommended use cases
Reorganizing ETL processes for better performance.Merging data from multiple pipelines into a single pipeline.Adjusting table refresh frequencies based on data needs.
Limitations · remember
!Standalone materialized views and streaming tables cannot be moved.
!Append once flows are not supported and must be removed from the destination pipeline.
!Private tables or views cannot be moved.
Architecture
Unity Catalog → Lakeflow Pipelines → Spark Declarative Pipelines
Get started
1
Stop Source Pipeline
Ensure the source pipeline is not running before moving tables.
2
Remove Table Definition
Delete the table's definition from the source pipeline's code.
3
Run ALTER Command
Execute the SQL command to reassign the table to the destination pipeline.
4
Add Table Definition to Destination
Insert the table's definition into the destination pipeline's code.
5
Run Both Pipelines
Start both pipelines to ensure the destination pipeline updates the table.
Key takeaway
The ability to move tables between pipelines enhances data management flexibility and operational efficiency.
2025-07-24-d1eb3a9d Generated by the Databricks Updates Agent · browse all updates