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

MADR decision record for moving cross-database macros into dbt-core + adapters #615

Merged
merged 3 commits into from
Jul 13, 2022

Conversation

dbeatty10
Copy link
Contributor

@dbeatty10 dbeatty10 commented Jun 26, 2022

This is a:

  • documentation update
  • bug fix with no breaking changes
  • new functionality
  • a breaking change

All pull requests from community contributors should target the main branch (default).

Description & motivation

See ADR-0002 for details.

@dbeatty10 dbeatty10 marked this pull request as ready for review June 26, 2022 00:50
@dbeatty10 dbeatty10 requested a review from jasnonaz June 27, 2022 00:07
@dbeatty10 dbeatty10 requested a review from joellabes July 6, 2022 13:29
Copy link
Contributor

@joellabes joellabes left a comment

Choose a reason for hiding this comment

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

This looks pretty good! It doesn't reflect the decision to move the load_by_period macro into the experimental features repo though. So in reality we made several decisions:

  • Keep tests and macros together
  • Move experiments to their own repo
  • Move cross-db macros to Core/adapters

* Good, because common, reusable functionality that differs across databases will work "out of the box"
* Good, because functionality can subjected to more [rigorous testing](https://docs.getdbt.com/docs/contributing/testing-a-new-adapter)
* Good, because we hope that many package vendors could drop their dependencies on `dbt_utils` altogether, which makes version resolution easier
* Good, because it's slightly more convenient to reference the macro as `dateadd` instead of `dbt_utils.dateadd`
Copy link
Contributor

Choose a reason for hiding this comment

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

I think I intend to always document them as dbt.dateadd() so that it's clear that they're coming from somewhere as opposed to magic macros, so this is maybe a neutral IMO

@joellabes
Copy link
Contributor

I like the DACI table at the top of the page 😍

@dbeatty10 dbeatty10 requested a review from joellabes July 12, 2022 23:17
Copy link
Contributor

@joellabes joellabes left a comment

Choose a reason for hiding this comment

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

love it LETSGOOOOO

@dbeatty10 dbeatty10 merged commit b20c96c into main Jul 13, 2022
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