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

ADAP-542: Add configuration options for dynamic tables #636

Merged

Conversation

mikealfare
Copy link
Contributor

@mikealfare mikealfare commented May 27, 2023

resolves #603

Description

  • add refresh_strategy and lag as configuration options
  • handle the interaction of these options via relation and ddl

Checklist

@mikealfare mikealfare added the Skip Changelog Skips GHA to check for changelog file label May 27, 2023
@mikealfare mikealfare self-assigned this May 27, 2023
@cla-bot cla-bot bot added the cla:yes label May 27, 2023
@mikealfare mikealfare marked this pull request as ready for review June 8, 2023 00:17
@mikealfare mikealfare requested a review from a team as a code owner June 8, 2023 00:17
@mikealfare mikealfare requested review from McKnight-42 and removed request for McKnight-42 June 8, 2023 00:17
@mikealfare mikealfare merged commit 9111c25 into feature/dynamic-tables/adap-544 Jun 8, 2023
@mikealfare mikealfare deleted the feature/dynamic-tables/adap-542 branch June 8, 2023 00:32
colin-rogers-dbt pushed a commit that referenced this pull request Jun 8, 2023
* create feature branch, point to core feature branch, add changie

* ADAP-541: Stub out dynamic table (#616)

* stub jinja templates with a traditional table as proxy
* add dynamic_table as a relation type
* setup testing framework for dynamic tables

* updated dbt-snowflake to reflect changes in dbt-core

* ADAP-542: Add configuration options for dynamic tables (#636)

* add new config enums

* added refresh strategy query and relation method to determine differences

* added dynamic table ddl

* tests mostly pass, fail due to dynamic table being unavailable

* updated with materialized views pushed to main, added retry to get_row_count for dynamic table initialization

* lag > target_lag; remove refresh statement that wasn't doing anything

* fixed some typos, readability updates on tests
@ytschang
Copy link

Regarding the refresh options (nowait and refresh), could there be a 3rd option called force or immediate? The behavior would be to perform a manual refresh on the dynamic table, rather than wait for the lag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla:yes Skip Changelog Skips GHA to check for changelog file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants