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

Community

Connector Improvement: Being able to de-select SUB TABLES

Planned
Babak Mahjoub User

disabling the columns within a table will not stop the table from syncing (My case is in Shopify connector)

i.e. I want to stop sub-table: order_note_attribute which causes a huge impact on MAR usage. yet it is not possible to stop this sub-table unless stopping the whole ORDER table!.

would be perfect if this feature is added. It is not limited to shopify and this example.  I have encountered more like this. 

Thanks!

Please sign in to leave a comment.

Comments

5 comments

Date Votes
  • Official comment
    Sandeep Preetam Saila Fivetranner

    Hi Everyone,

    Thank you for your feedback regarding the ability to de-select sub-tables within connectors like Shopify. We have received multiple similar requests and are pleased to inform you that we are rolling out universal table/column selection to address these concerns. I will ensure to track the progress closely and share updates with you as the rollout continues.

    Best,  
    Sandeep

  • Katrina L User

    Another specific example of this that we encountered was the product_tag table. We use the top level product table and product_variant of the sub tables, but not product_image, product_tag, or product_option and these drive >90% of the MAR we see for some Shopify customers.

    Given the schema it doesn't even look like they should be required for Product.

  • Bryan Estrada User
    • Edited

    I echo this request. The absence of this feature causes your connectors to have exhaust a lot of unnecessary MAR.

    Relatedly, I suspect that a "free" resync causes downstream child tables to sync and count against paid MAR. Whatever Fivetran does to implement this separation of child-tables must also take the resync scenario into account -- i.e. if a resync occurs on a parent table, either propagate the "freeness" downstream or else allow the caller to specify that downstream tables do not get resynced.

    For example, if a Fivetran employee were to trigger a resync of the `ORDER` table, then of course that table's MAR will be free for the duration of the resync. But child tables like `ORDER_LINE`, `ORDER_URL_TAG`, etc.. will also be synchronized consuming Paid MAR.

  • Bryan Estrada User

    Here is another side-effect of the UI that fivetran presents when these "child tables" are selectable / de-selectable.

    A user can disable those checkboxes in the hope of reducing MAR, but that won't work. But it looks like it will do something. Turns out, that because the primary key column(s) effectively cannot be disabled on child tables, the rows will still write but with empty data.

    This means that Fivetran's UI enables a situation where a user can choose to spend MAR to sync empty rows. Either implement this feature request or make this configuration impossible. I can think of zero scenarios where a user would on purpose want to make this configuration.

  • Jake Mullins User

    Any updates on this new feature availability? This field/subtable makes up the bulk of the cost for our shopify connection.