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

Community

Fivetran Platform connector should populate SOURCE_TABLE

Not planned
Jason Van Pee User

Which connector?:

Fivetran Platform Connector (Fivetran Platform Connector)

Additional details:

We utilize Atlan for asset lineage.  The tables populated by the Fivetran Platform Connector (ex: incremental_mar, connection, destination, log) do not show lineage back to Fivetran.  After discussing with Atlan support the reason for the missing lineage is the Fivetran Platform Connector tables do not have data in the SOURCE_TABLE table relating to where they are sourced from.

I would like the Fivetran Platform Connector to write data to the SOURCE_TABLE about itself like other connectors do.

Example of missing data:
SELECT COUNT(*)
FROM <database>.<schema>.SOURCE_TABLE
WHERE connection_id = '<fivetran platform connector connection id>';
-- returns 0

Thank you!

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Dipti Ranjan Sahoo Fivetranner

    Hi there,

    Thanks for sharing this. "Fivetran Platform connector should populate SOURCE_TABLE" is not currently on our roadmap.

    Upvotes and use-case detail are the primary way we gauge customer demand — every vote directly strengthens the case to build this. If others in the community share this need, please encourage them to upvote too.

    Could you share more about your specific use case? Understanding the underlying problem helps us revisit prioritisation as the landscape changes.

    Thanks,
    Dipti

  • Jason Van Pee User

    Thanks for the response.

    We utilize Atlan for asset lineage.  The tables populated by the Fivetran Platform Connector (ex: incremental_mar, connection, destination, log) do not show lineage back to Fivetran.  Ideally Atlan would show the source of these tables is Fivetran and in order for that to happen SOURCE_TABLE must be populated.

    Thank you!

    Jason