SteNicholas opened a new issue, #1426:
URL: https://github.com/apache/paimon-rust/issues/1426

   ### Search before asking
   
   - [x] I searched existing issues and pull requests. No open issue or active 
PR for persistent DROP FUNCTION was found on November 17, 2026.
   
   ### Motivation
   
   Rust supports creating, listing, resolving and executing persistent SQL 
scalar functions in a Paimon REST Catalog, but it does not expose the 
corresponding drop path. The Catalog trait and REST client provide 
create/get/list operations, and DataFusion documents persistent DROP FUNCTION 
as unsupported.
   
   With a REST Catalog configured, users should be able to complete the 
function lifecycle:
   
   ```sql
   CREATE FUNCTION paimon.test_db.plus_one(x INT)
   RETURNS INT
   RETURN x + 1;
   
   DROP FUNCTION paimon.test_db.plus_one;
   DROP FUNCTION IF EXISTS paimon.test_db.plus_one;
   ```
   
   Java already supports this through 
[RESTCatalog.dropFunction](https://github.com/apache/paimon/blob/00b4d05a6cc118091a38eeca23549519cfb775f4/paimon-core/src/main/java/org/apache/paimon/rest/RESTCatalog.java#L1251-L1262)
 and 
[RESTApi.dropFunction](https://github.com/apache/paimon/blob/00b4d05a6cc118091a38eeca23549519cfb775f4/paimon-api/src/main/java/org/apache/paimon/rest/RESTApi.java#L1759-L1773).
   
   ### Solution
   
   Start with persistent function deletion through the REST Catalog client and 
SQLContext.
   
   - Add a `Catalog::drop_function(identifier, ignore_if_not_exists)` 
operation, with an Unsupported default for catalogs that do not support 
persistent functions.
   - Add the REST DELETE request using the existing function resource path, 
authentication, prefix and identifier-encoding rules. Avoid a GET-before-DELETE 
existence check.
   - Implement RESTCatalog error mapping consistently with Java and existing 
Rust function lookups. Missing functions should error without IF EXISTS and be 
ignored with it; authentication, authorization, transport and 
unsupported-service errors must remain visible.
   - Route `DROP FUNCTION [IF EXISTS] name` through SQLContext. Resolve bare, 
two-part and three-part names consistently with CREATE FUNCTION, preserving 
quoted identifiers and the current catalog/database.
   - Start with one persistent function name per statement. Reject unsupported 
signatures/overload lists, modifiers or multi-target forms explicitly. Session 
UDFs must not be accidentally deregistered.
   - Update the SQL guide and REST Catalog capability documentation.
   
   Suggested validation:
   
   - Mock REST tests for one correctly encoded DELETE request, success, missing 
functions, permission failures, server/transport failures and unsupported 
services.
   - IF EXISTS suppresses only the intended missing-function error.
   - SQL resolution for bare/qualified names, quoted identifiers and 
non-default catalog/database settings.
   - Create/call/drop followed by a qualified catalog-function lookup failure, 
while an unrelated session UDF remains usable.
   - Non-REST catalogs and unsupported DROP FUNCTION syntax fail clearly.
   
   ### Anything else?
   
   Rust references:
   
   - [Catalog function 
operations](https://github.com/apache/paimon-rust/blob/1920eab1c60d2b5680fb767dbd60ae0cf668db78/crates/paimon/src/catalog/mod.rs#L685-L715).
   - [REST function client 
operations](https://github.com/apache/paimon-rust/blob/1920eab1c60d2b5680fb767dbd60ae0cf668db78/crates/paimon/src/api/rest_api.rs#L603-L677).
   - [RESTCatalog function 
implementation](https://github.com/apache/paimon-rust/blob/1920eab1c60d2b5680fb767dbd60ae0cf668db78/crates/paimon/src/catalog/rest/rest_catalog.rs#L623-L650).
   - [DataFusion documented function 
scope](https://github.com/apache/paimon-rust/blob/1920eab1c60d2b5680fb767dbd60ae0cf668db78/crates/integrations/datafusion/README.md#rest-catalog-views-and-sql-functions).
   
   Related: #499 added persistent CREATE FUNCTION. ALTER FUNCTION, overloaded 
function support, additional function kinds and implementing a new function 
service in the standalone Rust REST server are outside this first change.
   
   Source baseline: paimon-rust `1920eab1c60d2b5680fb767dbd60ae0cf668db78`, 
compared with Java Paimon `00b4d05a6cc118091a38eeca23549519cfb775f4`.
   
   ### Willingness to contribute
   
   - [ ] I'm willing to submit a PR!
   


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

Reply via email to