JingsongLi opened a new pull request, #1277: URL: https://github.com/apache/paimon-rust/pull/1277
### Purpose Closes #1273. Queries using registered DataFusion functions should not require permission to read REST catalog function metadata. For example, `SELECT count(*)` must work when the REST function API returns Forbidden. ### Brief change log - Resolve bare registered scalar, aggregate, and window function names locally, including aliases and session UDFs. - Apply the same precedence in nested REST functions, persistent views, time-travel queries, and function validation. - Preserve explicit catalog lookup errors and CREATE FUNCTION recursion checks. Explicit catalog calls cannot rebind a nested local function with the same name. ### Tests - Added four behavioral regressions covering denied REST lookup, nested calls/views, qualified name collisions, and permission-error preservation. - Confirmed the local-function regression fails on the original implementation with a Forbidden error. - Passed `TZ=UTC RUST_MIN_STACK=16777216 cargo test --locked -p paimon-datafusion --all-targets`. - Passed `cargo clippy --locked --no-deps -p paimon-datafusion --all-targets -- -D warnings` and formatting checks. ### API and Format No storage format or public API changes. Bare function resolution now follows the DataFusion registry before REST lookup; explicit three-part calls retain catalog semantics. ### Documentation Documented resolution precedence and error propagation in the DataFusion README. -- 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]
