feat: Implement non-partitioned tmp table #405
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Resolves: #396
Currently we have partitioned temp table creation for table and increment materialisation.
However this can lead to over price and over resources consumption as model's sql can be complicated. So that batches split run on this complicated sql may be not the very optimal way.
This PR implements the logic when we skip partitioning config while creating new tmp table and then we calculate batches and run insert statement based on this non-partitioned table.
Models used to test
table iceberg
increment iceberg
table hive
Checklist