Submaterializations

[acurtis-evi]

resolves #7122

Description

In my company, we have a need to run operations on our materialized tables such as user deletion requests. The dbt run-operation is single threaded and doesn't take advantage of the node yml structure. Other submaterializations might be things like 'clone' which just implements snowflake's clone feature.

I was thinking that an improvement would be to (for a particular model)

materialized: incremental
submaterializations:
  - user_delete
  - clone

Another model might be

materialized: table
submaterializations:
  - user_delete

Materializations named incremental_user_delete and table_user_delete could be created to match above

And it could be run using

dbt run --submaterialization user_delete ...

or

dbt ls --submaterialization user_delete ...

(also compile, parse)

Any model which has the submaterialization would respond to the above run and it would use the dag order / threads to run the operation.

https://getdbt.slack.com/archives/C50NEBJGG/p1677938569851409

Also supports --select submaterialization: syntax.

Checklist

• I have read the contributing guide and understand what's expected of me
• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

[github-actions]

This PR has been marked as Stale because it has been open with no activity as of late. If you would like the PR to remain open, please comment on the PR or else it will be closed in 7 days.

[github-actions]

Although we are closing this PR as stale, it can still be reopened to continue development. Just add a comment to notify the maintainers.