NO-SNOW: Fix UDF parameter registration error#4064
Merged
sfc-gh-joshi merged 3 commits intomainfrom Feb 13, 2026
Merged
Conversation
changelog revert ceiling change, fix udf error add missing max_batch_size arg
9759bcd to
cacf5a0
Compare
sfc-gh-bkogan
approved these changes
Feb 10, 2026
sfc-gh-mayliu
approved these changes
Feb 13, 2026
sfc-gh-heshah
approved these changes
Feb 13, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Which Jira issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
Fixes SNOW-NNNNNNN
Fill out the following pre-review checklist:
Please describe how your code solves the related issue.
Fixes a very minor bug where positional parameters are not passed correctly during UDF registration through
register_from_file, causingstrictandsecureto improperly be set. This was exposed while testing a pre-release version of protobuf for #4056, but that fix is no longer needed since protobuf released a compatible patch release that requires no action on our part.