REST: Add specific-name to UDF definition - #17364
Open
szehon-ho wants to merge 1 commit into
Open
Conversation
Align the REST FunctionDefinition schema with the optional specific-name field in the UDF specification. Generated-by: Codex
singhpk234
approved these changes
Jul 25, 2026
singhpk234
left a comment
singhpk234
left a comment
Contributor
There was a problem hiding this comment.
+1, thanks @szehon-ho !
amogh-jahagirdar
approved these changes
Jul 25, 2026
amogh-jahagirdar
left a comment
amogh-jahagirdar
left a comment
Contributor
There was a problem hiding this comment.
Thanks @szehon-ho, this looks good to me!
huaxingao
approved these changes
Jul 25, 2026
Member
Author
|
As this already passed the vote for adding it to the UDF spec, this just mirrors it, so seems minor and not worth a vote. Will merge unless someone disagrees. |
dramaticlly
approved these changes
Jul 28, 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
6 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.
Adds the optional
specific-namefield to theFunctionDefinitionschema in the REST catalog OpenAPI spec, aligning it with the UDF specification.specific-namewas added to the UDF spec in #16727 as an optional, user-assignable name for a single definition, analogous to the SQL standard's routine specific name. It gives a definition a stable handle that is independent of its signature, for statements such asDROP SPECIFIC FUNCTION. When present, it must be unique among all definitions within the UDF metadata.The field is optional and is therefore not added to the
requiredlist.rest-catalog-open-api.pyis regenerated accordingly.