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

Update date data type casting #103

Merged
merged 16 commits into from
Aug 30, 2023
Merged

Conversation

fivetran-reneeli
Copy link
Contributor

@fivetran-reneeli fivetran-reneeli commented Aug 22, 2023

PR Overview

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

This PR will result in the following new package version:

0.11.2

Non breaking as these changes are under the hood and will not have visible impact on downstream model materializations.
This will also be in combo with PR #51 in the source

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

  • Update seeds and configs in the integration testing folder to match what was updated in the [source]( PR #51)

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 (if applicable)

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.
  • You have provided details below around the validation steps performed to gain confidence in these changes.

Models should successfully run. Additionally will ask the customer to run on this branch as well.

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
  • [n/a] README updates have been applied (if applicable)
  • [ n/a] DECISIONLOG updates have been updated (if applicable)
  • [ n/a] 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?

💃

CHANGELOG.md Outdated Show resolved Hide resolved
Copy link
Contributor

@fivetran-avinash fivetran-avinash left a comment

Choose a reason for hiding this comment

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

looks good with one small commit update! Make sure to revert packages.yml and test that buildkite passes before merging/releasing.

@fivetran-reneeli
Copy link
Contributor Author

reminder to change package deps before merging

Copy link
Contributor

@fivetran-avinash fivetran-avinash left a comment

Choose a reason for hiding this comment

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

@fivetran-reneeli Re-reviewed! Left a few comments.

CHANGELOG.md Outdated
@@ -1,3 +1,7 @@
# dbt_quickbooks v0.11.2
Copy link
Contributor

Choose a reason for hiding this comment

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

@fivetran-reneeli Since we're not cutting a new release, would recommend making this like dbt_quickbooks v0.VERSION.VERSION since the next release could go to 0.11.2 or 0.12.0.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

oh good point, it'll serve as a good reminder as well. updated!

dbt_project.yml Outdated
@@ -1,7 +1,7 @@
config-version: 2
name: 'quickbooks'

version: '0.11.1'
version: '0.11.2'
Copy link
Contributor

Choose a reason for hiding this comment

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

Would just keep this as 0.11.1

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good point

@@ -1,6 +1,6 @@
name: 'quickbooks_integration_tests'

version: '0.11.1'
version: '0.11.2'
Copy link
Contributor

Choose a reason for hiding this comment

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

Would just keep this as 0.11.1

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good point

packages.yml Outdated
version: [">=0.9.0", "<0.10.0"]
# - package: fivetran/quickbooks_source
# version: [">=0.10.0", "<0.11.0"]
- git: https://github.com/fivetran/dbt_quickbooks_source.git
Copy link
Contributor

Choose a reason for hiding this comment

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

standard reminder to revert before merging. Would recommend kicking off Buildkite again after the source branch is merged to make sure it works on the new version

@@ -61,9 +61,16 @@ vars:
quickbooks_vendor_credit_identifier: "vendor_credit_data"
quickbooks_vendor_identifier: "vendor_data"

using_purchase_order: True
Copy link
Contributor

Choose a reason for hiding this comment

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

Are these variables needed now? Or were they just used for testing?

(Not that the integration tests is used by outside customers, but I'm not sure if we want to set the alternative variable logic as the default for future dev work.)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah I think that was there for testing. I'll remove it though

@@ -1,5 +1,5 @@
bill_payment_id,index,_fivetran_synced,amount,bill_id,check_id,credit_card_charge_id,credit_card_credit_id,deposit_id,expense_id,journal_entry_id,linked_bill_payment_id,vendor_credit_id,bill_payment_credit_card_id
23,0,2020-05-20 14:03:30,38757,19,,,,,,,,,
23,0,2020-05-20 14:03:30,38757,19.25,,,,,,,,,
Copy link
Contributor

Choose a reason for hiding this comment

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

This is weird. I see the original value in the source seed file is 19.25 too, but why is bill_id a decimal? I might just recommend pushing both back to 19.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ooh good catch, I'm not sure why that's there. I'll change those to 19

@fivetran-avinash
Copy link
Contributor

@fivetran-reneeli New changes look good to me!

CHANGELOG.md Outdated
@@ -1,3 +1,7 @@
# dbt_quickbooks v0.VERSION.VERSION
[This PR](https://github.com/fivetran/dbt_quickbooks/pull/103/files) includes the following updates:
Copy link
Contributor

Choose a reason for hiding this comment

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

should it be

Suggested change
[This PR](https://github.com/fivetran/dbt_quickbooks/pull/103/files) includes the following updates:
[PR #103](https://github.com/fivetran/dbt_quickbooks/pull/103/files) includes the following updates:

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated!

CHANGELOG.md Outdated
@@ -1,3 +1,7 @@
# dbt_quickbooks v0.VERSION.VERSION
Copy link
Contributor

Choose a reason for hiding this comment

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

if we are updating the packages.yml we gotta cut a release for the transform

Copy link
Contributor Author

Choose a reason for hiding this comment

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

True, updated this

@fivetran-reneeli fivetran-reneeli merged commit 74da53b into main Aug 30, 2023
1 check passed
@fivetran-reneeli fivetran-reneeli deleted the bugfix/cast_data_types_dates branch August 30, 2023 21:32
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.

3 participants