huaxingao opened a new pull request, #17966:
URL: https://github.com/apache/iceberg/pull/17966

   
   
   Follow-up to #15180, which added listFunctions and loadFunction. This adds
   the remaining function lifecycle operations that do not require a metadata
   update model:
   
   - createFunction (POST .../functions)
   - dropFunction (DELETE .../functions/{function})
   - functionExists (HEAD .../functions/{function})
   
   createFunction takes a new CreateFunctionRequest carrying the function name
   and its definitions. The server assigns function-uuid, format-version and
   definition-log, so those are not part of the request. Within each definition
   the server also assigns definition-id, current-version-id, and each version's
   version-id and timestamp-ms, replacing any values sent by the client. This
   mirrors CreateViewRequest, which embeds a full ViewVersion and documents the
   server replacing schema-id. createFunction returns the loaded function so
   clients do not need a follow-up load to learn the assigned UUID and metadata
   location.
   
   Errors use IcebergErrorResponse to match the existing function endpoints, and
   a FunctionAlreadyExistsError example is added for the 409 case.
   
   updateFunction is left for a follow-up, since committing changes to a 
function
   requires a metadata update and requirement model that the UDF spec does not
   define yet. Until it lands there is no in-place update: modifying a function
   means dropFunction followed by createFunction, which is not atomic, mints a
   new function-uuid, and does not preserve definition-log. Rename is also
   deferred: the function endpoints use CatalogObjectIdentifier while
   RenameTableRequest uses TableIdentifier, and which shape rename should use is
   worth settling separately.


-- 
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]

Reply via email to