huaxingao opened a new issue, #16700: URL: https://github.com/apache/iceberg/issues/16700
**Background** While reviewing the REST spec PR for list/load function endpoints (#15180), @szehon-ho raised (with SQL-standard input from @srielau) the idea of adding a "specific name" to the UDF function definition model. In the SQL standard, a routine has: a routine name — the user-facing function name, which may be shared across overloads, and a specific name — a unique name identifying a single overload. **Current state** The model already has definition-id, which uniquely identifies one overload within a function (each FunctionDefinition carries its own definition-id). This effectively fills the SQL "specific name" role today. **Proposal to discuss** Add an optional specific-name field on the function definition model as a convenience alongside definition-id, so engines can agree on a stable, human-readable name for a given overload (rather than only the opaque definition-id). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
