JingsongLi opened a new pull request, #1429:
URL: https://github.com/apache/paimon-rust/pull/1429

   ### Purpose
   
   Support dropping persistent REST Catalog functions through `SQLContext`. 
Previously, `DROP FUNCTION db.fn` was rejected by DataFusion, while bare names 
reached its local function registry.
   
   ### Brief change log
   
   - Support `DROP FUNCTION [IF EXISTS]` with bare, database-qualified, and 
catalog-qualified names, using a direct REST DELETE without an existence lookup.
   - Preserve local functions with colliding names and propagate permission, 
service, and unsupported-endpoint errors.
   - Reject unsupported temporary drops, signatures, multiple targets, and 
cascade/restrict modifiers before deletion. Handle leading empty statements and 
comments, reject dot path segments, and preserve `Send` SQL futures.
   
   ### Tests
   
   773 tests passed across DataFusion unit tests, SQL integration tests, 
table-type routing, REST API tests, and REST Catalog tests:
   
   ```sh
   RUST_MIN_STACK=16777216 CARGO_PROFILE_TEST_DEBUG=0 cargo test --locked -p 
paimon-datafusion --lib --test sql_context_tests --test table_type_routing
   RUST_MIN_STACK=16777216 CARGO_PROFILE_TEST_DEBUG=0 cargo test --locked -p 
paimon --test rest_api_test --test rest_catalog_test
   cargo fmt --all -- --check
   git diff --check
   ```
   
   Regression coverage includes name resolution, local-function isolation, 
temporary-drop safety, URL path validation, 204 responses, error preservation, 
and compile-time `Send` checks.
   
   ### API and Format
   
   Adds `Catalog::drop_function` with a default `Unsupported` implementation 
and `RESTApi::drop_function`. No storage-format changes.
   
   ### Documentation
   
   Updates `docs/src/sql.md` and the DataFusion README with supported syntax 
and limitations.
   
   


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