Skip to main content

Community

Connector Improvement: Support gzipped response from Azure Functions

Answered

Please sign in to leave a comment.

Comments

3 comments

  • Official comment

    Thanks Sven,

    Handling large responses efficiently is one of the things that led us to introduce our new Connector SDK. Getting the data from the source and passing to Fivetran while checkpointing regularly should allow Connector SDK to much more easily address this type of very large use case.

    We will continue to consider prioritizing gzip support for function connectors in our roadmap.

    Best regards
    Alison

    Hi Sven,

    Thank you for taking the time to submit the request. Can you share more about the connector you are writing that is producing responses over 100MB and gzipped and your full use case?

    This will help us prioritize the ask in our roadmap.

    Best regards

    Alison

    Hi Alison,

    Thank you for your reply!

    The connector we were trying to write is an Azure Function that extracts data from a remote API. The application behind this API uses event-sourcing (registers all changes to all models). The event-sourcing and just sheer amount of data ends up being a lot of data.

    We already configured the function to only retrieve data on a day-to-day basis but then it still is going over the ~100MB limit.

    Does this answer your question?

    Many thanks,
    Sven