Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Destination Improvement: Configure or Disable VACUUM for Databricks Destinations

Planned
Hector Guillermo Vazquez Rivas User

We’ve encountered challenges with the automatic VACUUM operation in Databricks destinations, as it interferes with our use of Change Data Feed (CDF) for incremental processing. We’d like to request the ability to disable VACUUM; and if it's on, be able to configure its schedule to avoid conflicts with downstream workloads.

This flexibility would help customers like us who rely on CDF maintain data integrity and control over retention timing.

Thank you for considering this feature enhancement.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Egidio Terra Fivetranner
    Hi Hector,

    Thank you so much for sharing this feature request regarding the ability to configure or disable VACUUM for Databricks destinations. We appreciate you taking the time to help us improve Fivetran, and we agree this is a valuable idea.

    I've added your request to our feature improvements backlog for further evaluation. Are you encountering any particular issues or inefficiencies with the current VACUUM process, or do you have requirements around scheduling or retention that would benefit from more control?

    We want to make sure any solution we consider will best support your workflow, so any additional details you can provide would be helpful.

    We’ll keep this thread updated with any progress or changes related to this feature. Thanks again for your input!

    Best regards,
    Egidio Terra