Set relation_column_encoding to AUTO by default #698
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
User-visible Changes
This changes the default of the
relation_column_encoding
setting fromON
toAUTO
. This means that Arthur will pick appropriate encodings for columns. (The encoding value is picked based on the type and whether it's used in distribution or sort keys.) Selecting the encoding speeds up loading data (COMPUPDATE
can be left off).Links
Closes #229
Testing
You can check the active setting using:
You can check which encoding is used with
show_ddl
on a table. Unless you already had the auto setting active, you would see for example columns like this:but then would see an encoding with the new default:
Deploy Notes
If the
relation_column_encoding
is set toAUTO
in local configurations, then this can be removed now. If this mode is not desired, thenrelation_column_encoding
must be set toOFF
now.Harry's internal note: This has been effectively in place in production given that we have a file in the object store with this content:
(This file should now be removed.)