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

Community

Connector Improvement: Replicate deletes from Azure Blob Storage connector.

Answered
Gaston Uriarte User

Would be great if when we delete a blob from the Azure Blob Storage the destination table would also update the data.

We use Fivetran to pull data from blobs that are in a Microsoft Azure container.
Every time that we create new blobs the data updates well in our destination table, but when we need to delete one of them, the blobs will still appear in the table even though they no longer exist in the container.

Is there a way where Fivetran can detect not only the changes where blobs are added, but also those where blobs are deleted?

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Alison Fivetranner

    Hi Gaston,

    Thank you for submitting this feature request. I'd be interested in understanding if you would be willing to pay more for this type of connector behavior?
    I ask because checking for or re-processing every file every sync in order to capture deletes could drive slow performance as well as high MAR.

    Can you share more about when types of data this would be useful for?

    Again I'm trying to understand if slow performance/high cost would make the feature effectively un-useable.

    Regards,

    Alison