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/netsuite2 #17

Merged
merged 61 commits into from
Jul 27, 2022
Merged

Feature/netsuite2 #17

merged 61 commits into from
Jul 27, 2022

Conversation

fivetran-jamie
Copy link
Contributor

@fivetran-jamie fivetran-jamie commented Jul 7, 2022

What change(s) does this PR introduce?

adds netsuite2 compatible staging models

things that still need to be done:

  • Change prefix of netsuite2 models to stg_netsuite2
  • Create new stg_netsuite2.yml file and document netsuite2 staging models (can leverage stg_netsuite.yml for tables that are also in the old schema, though note that they might have some new columns)
  • Add tests to staging models
  • Decide whether or not to add _netsuite2 suffix to all source table variables. Currently only new source tables (that james didn't bring in in Netsuite2.com Support #15)
  • Make seed data and get circle ci integration tests running
  • Do we want to add passthrough columns to any new tables?
  • changelog
  • readme documentation around the data_model var and netsuite vs netsuite2

Did you update the CHANGELOG?

  • Yes

no 😺

Does this PR introduce a breaking change?

  • Yes (please provide breaking change details below.)
  • No (please provide an explanation as to how the change is non-breaking below.)

no because the default data model is netsuite??? so nothing should change automatically for current users. but also this is a big change?

Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)

  • Yes

no, let's decide on the major vs minor change

Is this PR in response to a previously created Bug or Feature Request

How did you test the PR changes?

  • CircleCi
  • Local (please provide additional testing details below)

Select which warehouse(s) were used to test the PR

  • BigQuery
  • Redshift
  • Snowflake
  • Postgres
  • Databricks
  • Other (provide details below)

Provide an emoji that best describes your current mood

🏕️

Feedback

We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.

fivetran-joemarkiewicz and others added 24 commits July 11, 2022 10:28
Co-authored-by: Jamie Rodriguez <65564846+fivetran-jamie@users.noreply.github.com>
Co-authored-by: Jamie Rodriguez <65564846+fivetran-jamie@users.noreply.github.com>
Co-authored-by: Jamie Rodriguez <65564846+fivetran-jamie@users.noreply.github.com>
Co-authored-by: Jamie Rodriguez <65564846+fivetran-jamie@users.noreply.github.com>
Co-authored-by: Jamie Rodriguez <65564846+fivetran-jamie@users.noreply.github.com>
Co-authored-by: Jamie Rodriguez <65564846+fivetran-jamie@users.noreply.github.com>
Co-authored-by: Jamie Rodriguez <65564846+fivetran-jamie@users.noreply.github.com>
Co-authored-by: Jamie Rodriguez <65564846+fivetran-jamie@users.noreply.github.com>
Co-authored-by: Jamie Rodriguez <65564846+fivetran-jamie@users.noreply.github.com>
Copy link
Contributor

@fivetran-joemarkiewicz fivetran-joemarkiewicz left a comment

Choose a reason for hiding this comment

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

LGTM! Netsuite2 compatibility looks good to go!

@fivetran-jamie fivetran-jamie merged commit abb33e1 into main Jul 27, 2022
jmongerlyra pushed a commit to jmongerlyra/dbt_netsuite_source that referenced this pull request Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants