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

Community

Connector Improvement: Table Level Granularity for Gitlab connector

Completed
Lea Benyamin User

We've seen a high increase of our usage caused by the gitlab connector. We would like to sync fewer tables than what we sync today but it seems that there is no table granularity. We have this granularity for other connectors, would it be possible to develop it for gitlab connectors ? Thanks

Please sign in to leave a comment.

Comments

5 comments

Date Votes
  • Official comment
    Sanjeevv Maniram T Fivetranner

    Hi,

    Currently, there is no option to de-select child tables, but this functionality is expected to be available by the end of this quarter (likely February 2025). However, de-selection at the parent level is already available, allowing you to de-select those tables as needed.

    Additionally, we are working on a new feature in the setup form that will enable customers to limit the historical data they wish to sync. While we don't have a confirmed ETA for this feature, we are making every effort to implement it as soon as possible.

  • Yegor Ius User

    Related: another issue related to high data volumes from the GitLab connector https://support.fivetran.com/hc/en-us/community/posts/27091206660631-Connector-Improvement-GitLab-Connector-add-ability-to-control-how-far-back-usage-is-gathered

  • James Hartig User

    Yes, we'd like to remove the job-related tables because those generate tens of millions of MARs per month which is preventing us from using the GitLab connector.

  • Yegor Ius User

    James, you're lucky you have the choice of not using Fivetran for GitLab. We're stuck with it unfortunately because we need the telemetry from our CI/CD usage.

    I suppose this behavior is good for Fivetran, they're raking in the money we spend...

  • James Hartig User

    Thanks for the update Sanjeevv. If there's an early access or beta I'd love to participate.