JingsongLi opened a new pull request, #494: URL: https://github.com/apache/paimon-rust/pull/494
## What changed - add Paimon REST Catalog models, resource paths, pagination, and read APIs for persistent views and functions - expose existing REST views through DataFusion catalog providers with owning-namespace resolution, declared-schema alignment, and recursive dependency protection - expand deterministic REST SQL scalar functions before DataFusion planning, supporting bare and fully qualified names, nested functions, argument validation, return coercion, statement-local metadata caching, and cycle detection - document REST Catalog view and SQL function behavior in the DataFusion README and SQL integration guide ## Why `paimon-datafusion` previously treated persistent REST Catalog views as missing tables and could not resolve SQL functions stored in the catalog. This adds read-and-execute support for existing objects without introducing view or function DDL. ## User impact Queries executed through `SQLContext` can now read persistent REST views and call existing SQL scalar functions as either `function(...)` in the current namespace or `catalog.database.function(...)`. Unsupported definitions and unsafe shapes fail during planning with explicit errors. ## Validation - `cargo test -p paimon-datafusion --lib rest_` — 16 passed - `cargo test -p paimon --test rest_object_models_test` — 6 passed - `cargo test -p paimon --test rest_api_test` — 21 passed - RESTCatalog-focused tests — 31 passed - `cargo clippy -p paimon -p paimon-datafusion --lib --tests -- -D warnings` - `cargo fmt --all -- --check` - `mkdocs build --strict` The full `paimon-datafusion` library test run also reached 222 passing tests; seven existing scan tests could not load their expected `/tmp/paimon-warehouse` fixture metadata in this local environment. -- 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]
