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 typeid #109

Merged
merged 14 commits into from
Jun 8, 2023
Merged

Feature/add typeid #109

merged 14 commits into from
Jun 8, 2023

Conversation

fivetran-catfritz
Copy link
Contributor

@fivetran-catfritz fivetran-catfritz commented Jun 2, 2023

PR Overview

This PR will address the following Issue/Feature:
#106

This PR will result in the following new package version:

  • v0.10.0 - Adding columns to some tables that affect transform models.

Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:

  • Because of the May 2023 connector update type_id was added to DEAL_COMPANY and DEAL_CONTACT. These tables are not pulled into the transform package.

    • I also added column-combo tests for these tables since the update states these are meant to form a composite primary key.
  • Also resulting from the connector update, columns updated_at and created_at have been added to the following sources and their corresponding staging models:

    • DEAL_PIPELINE
    • DEAL_PIPELINE_STAGE
    • TICKET_PIPELINE
    • TICKET_PIPELINE_STAGE
  • These columns do get pulled into the transform package, for which I opened a PR on the transform.

PR Checklist

Basic Validation

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

  • dbt compile
  • dbt run –full-refresh
  • dbt run
  • dbt test
  • dbt run –vars (see ticket for vars used)

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

  • The appropriate issue has been linked and tagged
  • You are assigned to the corresponding issue and this PR
  • BuildKite integration tests are passing

Detailed Validation

Please acknowledge that the following validation checks have been performed prior to marking this PR as "ready for review":

  • You have validated these changes and assure this PR will address the respective Issue/Feature.
  • You are reasonably confident these changes will not impact any other components of this package or any dependent packages.
    • They will affect transform, which I have opened a PR for in the transform.
  • You have provided details below around the validation steps performed to gain confidence in these changes.
  • Validated using data provided in ticket and added tests mentioned above. This was a straight add of columns added by the connector. Ran the published package on our dataset, ran the updated package, and confirm the columns were added with no change in row count/grain.

Standard Updates

Please acknowledge that your PR contains the following standard updates:

  • Package versioning has been appropriately indexed in the following locations:
    • indexed within dbt_project.yml
    • indexed within integration_tests/dbt_project.yml
  • CHANGELOG has individual entries for each respective change in this PR
  • README updates have been applied (if applicable)
  • DECISIONLOG updates have been updated (if applicable)
  • Appropriate yml documentation has been added (if applicable)

dbt Docs

Please acknowledge that after the above were all completed the below were applied to your branch:

  • docs were regenerated (unless this PR does not include any code or yml updates)

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

🐈

@fivetran-catfritz fivetran-catfritz changed the base branch from main to release/v0.10.0 June 2, 2023 23:24
@fivetran-catfritz fivetran-catfritz self-assigned this Jun 6, 2023
@fivetran-catfritz fivetran-catfritz linked an issue Jun 7, 2023 that may be closed by this pull request
4 tasks
Copy link
Contributor

@fivetran-jamie fivetran-jamie left a comment

Choose a reason for hiding this comment

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

looks great! just a couple of documentation comments and random questions

CHANGELOG.md Outdated
Comment on lines 3 to 10
- In the [May 2023 connector update](https://fivetran.com/docs/applications/hubspot/changelog#may2023) `type_id` was added to sources `DEAL_COMPANY` and `DEAL_CONTACT` as a part of the composite primary key for these tables. This column has been adding to the corresponding staging models. ([PR #100](https://github.com/fivetran/dbt_hubspot_source/pull/100))
- Updated tests for these tables with `type_id` as part of the primary key. ([PR #100](https://github.com/fivetran/dbt_hubspot_source/pull/100))
- Also resulting from the connector update, columns `updated_at` and `created_at` have been added to the following sources and their corresponding staging models: ([PR #100](https://github.com/fivetran/dbt_hubspot_source/pull/100))
- `DEAL_PIPELINE`
- `DEAL_PIPELINE_STAGE`
- `TICKET_PIPELINE`
- `TICKET_PIPELINE_STAGE`
- Updated docs with these changes and a little housekeeping. ([PR #100](https://github.com/fivetran/dbt_hubspot_source/pull/100))
Copy link
Contributor

Choose a reason for hiding this comment

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

the PR references should be for PR #109 right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, thank you. Updated!

models/stg_hubspot__ticket.yml Outdated Show resolved Hide resolved
models/stg_hubspot__ticket.yml Outdated Show resolved Hide resolved
Copy link
Contributor

@fivetran-jamie fivetran-jamie left a comment

Choose a reason for hiding this comment

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

lgtm!

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