snowflake: add option to ignore null values in schema evolution #3211
+155
−53
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rockwotj
force-pushed
the
null_schema
branch
2 times, most recently
from
4ff37d7 to
cbf9ee4
Compare
mihaitodor
approved these changes
Feb 26, 2025
| @@ -121,6 +122,7 @@ ALTER TABLE t1 ADD COLUMN a2 NUMBER; | |||
| `), | |||
| service.NewObjectField(ssoFieldSchemaEvolution, | |||
| service.NewBoolField(ssoFieldSchemaEvolutionEnabled).Description("Whether schema evolution is enabled."), | |||
| service.NewBoolField(ssoFieldSchemaEvolutionIgnoreNulls).Description("If `true`, then new columns that are `null` are ignored and schema evolution is not triggered. If `false` then null columns trigger schema migrations in Snowflake. NOTE: unless you already know what type this column will be in advanced, it's highly encouraged to ignore null values.").Default(true).Advanced(), | |||
There was a problem hiding this comment.
Typo: advanced -> advance
Mor options! This allows folks to include nulls when managing the schema. If you are managing the schema explicitly (ie. using a schema in schema registry) this can make a lot of sense, by default we expect people to just throw data at the connector and we should just drop nulls because we don't know what type the column will eventually be.
rockwotj
force-pushed
the
null_schema
branch
from
cbf9ee4 to
a9b8ed0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Mor options! This allows folks to include nulls when managing the
schema. If you are managing the schema explicitly (ie. using a schema in
schema registry) this can make a lot of sense, by default we expect
people to just throw data at the connector and we should just drop nulls
because we don't know what type the column will eventually be.