compress_table: add in_place option for modifying column encodings w/o creating a deep copy #59
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 & motivation
Back in 2020, Redshift introduced support for modifying column compression encodings in-place (some details here & official documentation here), which can be preferable to the older mechanism of recreating the table with the optimal encodings from a deep copy in certain cases.
For the past 2.5ish years at Lattice, my team has been using this modified version of the compress_table macro to leverage this "new" Redshift feature (credit to @neddonaldson!).
Changes:
in_place
argument tocompress_table
that defaults to the existing deep copy behaviorbuild_optimized_definition
, returning the optimized definition (no change) and anupdated_encodings
column name: encoding dictalter_column_encodings
helper to modify column encodings w/ anALTER {{ table }} ALTER {{ column }}
statement whenin_place=True
and at least one encoding is due to changeExample logs from
build_optimized_definition
&alter_column_encodings
:Checklist