Fix safe type expansion for incremental models#731
Merged
Conversation
axellpadilla
force-pushed
the
fix/safe-type-expansion
branch
2 times, most recently
from
258a083 to
2203c55
Compare
…and add test for widening
axellpadilla
force-pushed
the
fix/safe-type-expansion
branch
from
2203c55 to
901d4f4
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Enhance type handling in incremental models by ensuring safe type expansion during schema changes. Update tests to validate the widening of types and assert correct metadata retrieval for columns. Adjust default configuration to enable safe type expansion when flag is enabled.