Destination Improvement: Support Liquid Clustering in databricks destination
CompletedCurrently Liquid Clustering is not supported in databricks destination tables, it is mentioned in the documentation as well as I've tested and we are getting errors if we cluster a table, we are sinking tables to Unity Catalog and then downstream application wants to pull this data and currently they are performing full scans in order to get the data they need.
Liquid clustering should speed up these queries significantly as well as speed up any processing which works on fivetran destination tables. It is now a GA feature for databricks users, so I imagine it should be a desired feature
-
Official comment
Hi Marcin,
I’m pleased to announce that Liquid Clustering is now available with Fivetran. You can enable it by setting the cluster keys directly in Databricks.
Best,
Egidio -
Hi Marcin,
Thank you for submitting this feature request and sharing your idea to support Liquid Clustering in the Databricks destination. We appreciate you taking the time to help us improve Fivetran, and we agree that this is a valuable suggestion.
I've added your request to our feature improvements backlog for further review. In order to better understand your needs, I’m curious to learn more about your use case—what specific challenges are you hoping Liquid Clustering will help address in your Databricks environment? Any details you can share about the problem you’re trying to solve or the outcomes you’re looking for would be very helpful for our evaluation.
We’ll make sure to keep this thread updated with any progress or changes regarding this feature.
Thank you again for your feedback!
Best regards,
Please sign in to leave a comment.
Comments
2 comments