You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As a Faros CE user, I want to apply transformations on what Airbyte writes against the Faros Schema to capture my idiosyncrasies.
Describe the solution you'd like
Support for dbt transforms in Airbyte: https://docs.airbyte.com/operator-guides/transformation-and-normalization/transformations-with-airbyte
This would allow the ability to write lightweight transforms in SQL for one's own consumption, but also publish and share those with the community for common use cases. For example, transforming tasks that have a certain label or type into incidents.
Describe alternatives you've considered
It is possible for Analysts in Metabase to transform the data with SQL, but they cannot write it back to the database. dbt transforms during ingestion allows users to leverage canned dashboards better, and provide better separation of concerns between the analyst and data engineer personas.
Is your feature request related to a problem? Please describe.
As a Faros CE user, I want to apply transformations on what Airbyte writes against the Faros Schema to capture my idiosyncrasies.
Describe the solution you'd like
Support for dbt transforms in Airbyte: https://docs.airbyte.com/operator-guides/transformation-and-normalization/transformations-with-airbyte
This would allow the ability to write lightweight transforms in SQL for one's own consumption, but also publish and share those with the community for common use cases. For example, transforming tasks that have a certain label or type into incidents.
Describe alternatives you've considered
It is possible for Analysts in Metabase to transform the data with SQL, but they cannot write it back to the database. dbt transforms during ingestion allows users to leverage canned dashboards better, and provide better separation of concerns between the analyst and data engineer personas.
Additional context
The text was updated successfully, but these errors were encountered: