cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

The best practice to remove old data from DLT pipeline created tables

LasseL
New Contributor II

Hi, didn't find any "reasonable" way to clean old data from DLT pipeline tables. In DLT we have used materialized views and streaming tables (scd1, append only). What is the best way to delete old data from the tables (storage size increases linearly, of course new measures comes every day and old data is not deleted... yet). Let say that we want do delete all measurement which measurement timestamp is older than one month.

4 REPLIES 4

Kaniz_Fatma
Community Manager
Community Manager

Hi @LasseL, To manage old data in Delta Live Tables (DLT), use a combination of Delta Lake's features and DLT capabilities: start by using Delta Lake's `DELETE` command to remove outdated records, for example, by deleting entries older than one month. Integrate this deletion logic into your DLT pipeline with a Python function that filters out old data. Schedule regular maintenance tasks using Databricks Jobs to automate this process. After deletion, run the `OPTIMIZE` command to enhance query performance and use `VACUUM` to clean up unused files and free up storage space. These steps will help keep your storage usage in check and ensure efficient data management.

This approach doesn't work with DLT, because the manual DELETE command immediately causes pipeline corruption. We have to use skipChangeCommits=True, but this option has several limitations, at least it cannot be used with apply_changes(). Is there any other approach to cleaning up old data in DLT?

LasseL
New Contributor II

Exactly, this is not a "trivial problem", one possible solution is take bronze out of DLT pipeline (to manage by yourself, for example structured streaming from source with skipChangeCommits and partitioned by year/month, what ever you want to do to make delete handling optional), then define silver layer in DLT with "full refresh/overwrite". Of course this not fit in all situations. Just gave some idea.

Rishabh-Pandey
Esteemed Contributor

One effective way is to use partitioning in your Delta tables based on the timestamp of your data. This way, you can take advantage of Delta Lakeโ€™s  Vacuum command to remove old files and reduce the size of your storage.

also vacuum and optimise command can be run on delta live Table.

Rishabh Pandey

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you wonโ€™t want to miss the chance to attend and share knowledge.

If there isnโ€™t a group near you, start one and help create a community that brings people together.

Request a New Group