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

Feature/add transformation runs #141

Open
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

fivetran-reneeli
Copy link
Contributor

@fivetran-reneeli fivetran-reneeli commented Dec 17, 2024

PR Overview

This PR will address the following Issue/Feature: internal ticket

This PR will result in the following new package version:

'1.11.0'
Introduction of a new table transformation_runs and aggregated model run information, coinciding with pricing update.

Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:

Schema Changes: Adding the transformation_runs table

  • We have added the transformation_runs source table. This includes the following updates:
    • Added a new staging stg_fivetran_platform__transformation_runs model. Additionally, a new tmp model stg_fivetran_platform__transformation_runs_tmp and get_transformation_runs_columns() macro to ensure all required columns are present in the new staging model.
    • Added the following fields to the fivetran_platform__usage_mar_destination_history end model for each destination and month:
      • paid_model_runs
      • free_model_runs
      • total_model_runs
    • Included documentation about the respective fields in the transformation_runs source table and the aggregated *_model_run fields.

Under the Hood

  • Added transformation_runs seed data in integration_tests/seeds/.

PR Checklist

Basic Validation

Please acknowledge that you have successfully performed the following commands locally:

  • dbt run –full-refresh && dbt test
  • dbt run (if incremental models are present) && dbt test

Before marking this PR as "ready for review" the following have been applied:

  • The appropriate issue has been linked, tagged, and properly assigned
  • All necessary documentation and version upgrades have been applied
  • docs were regenerated (unless this PR does not include any code or yml updates)
  • BuildKite integration tests are passing
  • Detailed validation steps have been provided below

Detailed Validation

Please share any and all of your validation steps:

hex notebook

If you had to summarize this PR in an emoji, which would it be?

💃

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.

1 participant