Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2025 03:46 AM
Liquid Clustering replaces manual partitioning and Z-Ordering with adaptive file clustering.
It keeps your data physically organized for faster queries and merges, without forcing you to manage partition columns or compaction jobs.
It’s powered by cluster-by keys, Delta’s internal clustering metadata, and automatic reclustering handled by the Delta optimizer.
Table Size Rough Range LC Benefit Notes
| Small | < 10 GB or < 50 million rows | Limited | Metadata overhead may outweigh benefit. Stick with Delta defaults or small Z-ORDER. |
| Medium | 10 GB – 1 TB or 50M–1B rows | Strong | Ideal range — LC improves scan times, merges, and compaction efficiency. |
| Large | > 1 TB or billions of rows | Very high | Major gains in data skipping and read performance, especially for multi-year or multi-tenant data. |
More you can find in the documentation. If you have a specific case, not generic, I am more than happy to advise.
https://docs.databricks.com/aws/en/delta/clustering
https://docs.databricks.com/aws/en/delta/best-practices
https://docs.databricks.com/aws/en/delta/optimize
