Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PLUS-1409] Introduce translator pattern for Fivetran #25557

Merged
merged 7 commits into from
Oct 30, 2024

Conversation

briantu
Copy link
Contributor

@briantu briantu commented Oct 25, 2024

Summary & Motivation

Our BI integrations (Power BI, Sigma, Tableau, Looker) and DBT integration use a translator pattern to allow users to customize the assets they load from the external tool. We want to do the same for Fivetran.

How I Tested These Changes

Changelog

[Fivetran] Introduced DagsterFivetranTranslator to customize assets loaded from Fivetran.

Copy link
Contributor Author

briantu commented Oct 25, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @briantu and the rest of your teammates on Graphite Graphite

@briantu briantu marked this pull request as ready for review October 25, 2024 20:37
@briantu briantu changed the title Introduce translator pattern for Fivetran [PLUS-1409] Introduce translator pattern for Fivetran Oct 29, 2024
Copy link
Member

@benpankow benpankow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙏 thanks for handling this

@briantu briantu merged commit e92a573 into master Oct 30, 2024
1 check passed
@briantu briantu deleted the briantu/fivetran-translator branch October 30, 2024 00:03
maximearmstrong added a commit that referenced this pull request Nov 8, 2024
…classes for rework (#25751)

## Summary & Motivation

~~Builds out a very barebones translator class for the new version of
the Fivetran integration.~~

~~The implementation for this translator will be inspired by the
`DagsterFivetranTranslator` introduced in
#25557, but a new
implementation is required to leverage the workspace context and
state-backed definitions, which is incompatible with the current
translator and way of building assets.~~

Edit after Ben's comment
[here](#25751 (comment)):

Move things around under translator.py. This PR leverages the
`DagsterFivetranTranslator` introduced in introduced in
#25557.
`FivetranWorkspaceData` will implement the method
`to_fivetran_connector_table_props_data` in a subsequent PR, that will
map raw connector and destination data fetched using the Fivetran API
into `FivetranConnectorTableProps` objects, that are compatible with the
translator. This process will match what we currently do.

## How I Tested These Changes

Tests will be added in subsequent PRs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants