WIP: changed the macro to work with snowflake

[nehiljain]

No description provided.

[clrcrl]

Hey @nehiljain — I'll dedicate some time on Friday to take a look at this

[clrcrl]

Hi Nehil! Thanks for this PR!

I had a poke around here this afternoon, and it turns out that since originally writing this code in 2018, we've made some improvements in dbt that simplifies the code needed for a materialization. I think rather than working at the edges of this code to get it to work across multiple warehouses, it's time for a refactor! I wrote up my thoughts in dbt-labs/dbt-labs-experimental-features#32.

As a result, I'm going to close this PR (as it does indeed break the Redshift implementation). If you'd like to help out on dbt-labs/dbt-labs-experimental-features#32, drop a note in the comments of that issue to let me know.

In the meantime, all is not lost! You can leverage this macro by adding it to your own project directly! Simply:

1. Copy the code into a file in the macros/ directory
2. Within this code, replace dbt_utils.get_period_boundaries with <project_name>.get_period_boundaries (since you want to use the get_period_boundaries macro in your project rather than in dbt_utils), grab your project name from your dbt_project.yml file (next to name:).

Alternatively, you can also maintain a fork of dbt-utils and install that in your project, but I'd recommend the above process.

Let me know if you encounter any issues!