Connector Improvement: GitLab Connector - add ability to control how far back usage is gathered
Answered
Request to specify time range of data gathering. We only need data on last 3 months.
In April GitLab connector usage skyrocketed. Looking at the breakdown I see that the costs are coming from project_job. I see at the 1st of each month there's a huge sync.
Our theory is that the sync is grabbing all historical data. If so, we don't need all of it and want to control how far it goes.
We opened a support ticket and were directed to create a feature request, as what we're asking for doesn't exist.
-
Official comment
Hi Yegor,
Thank you for your feature request regarding the GitLab connector.
We are currently in a private rollout of child table deselection across a limited set of connectors. As we move forward, this option will become more broadly available for all connectors.
In the meantime, please let us know whether you would still be interested in ingesting the historical data once this capability is available.
Thank you again for your valuable feedback -it plays a key role in shaping our roadmap.
Best regards,
Sisan -
Upvoted this request by Lea as well https://support.fivetran.com/hc/en-us/community/posts/26996340035991-Connector-Improvement-Table-Level-Granularity-for-Gitlab-connector since we'd like to completely exclude project_job_artifact from the connector but can't right now.
-
Would still like to see this implemented.
This issue https://support.fivetran.com/hc/en-us/community/posts/26996340035991-Connector-Improvement-Table-Level-Granularity-for-Gitlab-connector is more important though.
Please sign in to leave a comment.
Comments
3 comments