[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt-spark functionality, rather than a Big Idea better suited to a discussion
Describe the feature
When using the merge strategy in the incremental materialization, we first create a VIEW then reference this view in the MERGE operation. Perhaps I'm missing something, but wouldn't be better to inject the compiled SQL directly in the MERGE clause.
Describe alternatives you've considered
This can be esaly modified in the macro/materialization/incremental/strategies.sql file.
Who will this benefit?
This is can benefecial for data engineers since they won't have the view object to manage in the database.
Is this your first time submitting a feature request?
Describe the feature
When using the merge strategy in the incremental materialization, we first create a VIEW then reference this view in the MERGE operation. Perhaps I'm missing something, but wouldn't be better to inject the compiled SQL directly in the MERGE clause.
Describe alternatives you've considered
This can be esaly modified in the macro/materialization/incremental/strategies.sql file.
Who will this benefit?
This is can benefecial for data engineers since they won't have the view object to manage in the database.
Are you interested in contributing this feature?
Yes
Anything else?
No response