Suppress errors when SQL functions have SAFE. prefix #1
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
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.
zetasql tells us when a function had the SAFE. prefix, by setting the error mode on the function call node to SafeMode.
This makes a change to check the error mode, and for "normal" functions, calls a separate version that suppresses any errors. For other (aggregations or analytical) functions, it throws an error that safe mode is not supported.
See goccy/bigquery-emulator#149 for the issue this addresses in the upstream repo.
This helps unblock Recidiviz/recidiviz-data#15020