yujunjun/datahub
2
0
Fork 0
mirror of https://github.com/datahub-project/datahub.git synced 2025-11-02 11:49:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(fivetran): Update docs on connection mapping to source systems (#13256)

Browse Source
This commit is contained in:
Pedro Silva 2025-04-20 10:19:46 +01:00 committed by GitHub
parent e9a7d35cb8
commit 61a71de360
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 15 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
metadata-ingestion/docs/sources/fivetran/fivetran_pre.md
View File

@ -62,9 +62,22 @@ grant role fivetran_datahub to user snowflake_user;
### Working with Platform Instances
If you've multiple instances of source/destination systems that are referred in your `fivetran` setup, you'd need to configure platform instance for these systems in `fivetran` recipe to generate correct lineage edges. Refer the document [Working with Platform Instances](https://datahubproject.io/docs/platform-instances) to understand more about this.
If you have multiple instances of source/destination systems that are referred in your `fivetran` setup, you'd need to configure platform instance for these systems in `fivetran` recipe to generate correct lineage edges. Refer the document [Working with Platform Instances](https://datahubproject.io/docs/platform-instances) to understand more about this.
While configuration of platform instance for source system you need to provide connector id as key and for destination system provide destination id as key.
While configuring the platform instance for source system you need to provide connector id as key and for destination system provide destination id as key.
When creating the conection details in the fivetran UI make a note of the destination Group ID of the service account, as that will need to be used in the `destination_to_platform_instance` configuration.
I.e:
<p align="center">
<img width="70%" src="https://github.com/datahub-project/static-assets/raw/main/imgs/integrations/bigquery/bq-connection-id.png"/>
</p>
In this case the configuration would be something like:
```yaml
destination_to_platform_instance:
greyish_positive: <--- this comes from bigquery destination - see screenshot
database: <big query project ID>
env: PROD
```
#### Example - Multiple Postgres Source Connectors each reading from different postgres instance