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

Community

Connector Improvement: GitHub Connector Improvement - Allow "base" Tables to be Deselected in Schema

Joe Nelson User

In the GitHub connector, users are not allowed to deselect specific tables from the "Schema" tab. There is no checkbox to deselect specific tables, and the Fivetran UI states: "Cannot unselect - Core tables cannot be blocked", as in the screenshot below:

We would like to be able to deselect these core tables and only select what we plan to use. At a minimum, having less core tables would be helpful.

In our particular use case, we have no intention on using commit data. Syncing the `commit_file` table is taking an extremely long amount of time and has synced over one million rows so far, with more to come. One of the repositories we're been asked to sync has been around for nearly ten years and has tens of thousands of commits, and even more files changed in commits.

Please allow users to deselect core tables in the GitHub connector.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Erin Fivetranner

    Hi Joe - 
    Thanks for submitting this feature request! This definitely seems like a valid feature improvement. Often (not sure entirely for this connector) table level deselection is very complex due to having maintain cursors for each table. 

    I will discuss this more with our engineering team to better understand the technical implications. 
    Seeing as the commit_file is not particularly valuable to you, would you mind sharing what your use case for GitHub analytics data is? This helps me as a Product Manager to better understand what our customers find valuable in a given source.

    Thanks,
    Erin

  • Joe Nelson User

    Hi Erin - thanks for the response.

    We have two planned documentation-based (mainly) use cases for GitHub data right now. Our first case consists of using labels input on issues (specifically, PRs) for our documentation team's use. They track specific labels to expand our documentation when new features roll out.

    Second, we'd like to use issue body text for documentation expansion and other analyses of phrases and to track trends in issues.

    Hope that's helpful - thanks again.