Safe cast field to INT to avoid failure on casting error #217
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.
Failures in the
run-end-hook
are occurring in snowflake production because the extractedrows_affected
field from the manifest is a string and occasionally fails insertion into an INT columnAdding safe casting to avoid failure.
In our case, what's causing the failure is a custom materialization type called
insert_by_period
in a 3rd party package that's reporting the rows_affected as an empty string. Bigquery already has the casting implemented so it makes sense to add the same for snowflake!