fix: handle empty endpoints during cloud function reuse#17501
Merged
Conversation
sycai
approved these changes
Jun 17, 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes an issue where reusing recently created Cloud Functions during Remote Function creation would sometimes result in an empty endpoint (
endpoint="").When a Cloud Function has been recently provisioned, its endpoint URI (
response.service_config.uri) may occasionally be returned as an empty string if URL propagation is still pending. The remote function decorator previously only checked forNone, proceeding to create the BigQuery Remote Function withOPTIONS(endpoint=''), which leads to validation failures when queries invoke the function.This PR changes the check to
if not cf_endpoint:to handle bothNoneand empty strings. If the endpoint is empty, it will route tocreate_cloud_function, which catches theAlreadyExistsexception and safely retries/waits for the endpoint URI propagation to complete.Fixes #<525124882> 🦕