shyjsarah opened a new pull request, #518: URL: https://github.com/apache/paimon-rust/pull/518
## What changed - skip REST view fallback when a missing relation name matches a registered table function - keep ordinary table and REST view resolution unchanged - add a regression test using the built-in `vector_search` table function and a generic REST catalog ## Why DataFusion preloads relation names before planning. For a query such as `FROM vector_search(...)`, it may first ask the current schema for a table named `vector_search`. After REST view support was added in #494, a missing table was reinterpreted as a view, so a catalog error from `get_view` could abort planning before the registered table function was resolved. ## User impact Registered table functions are now resolved by DataFusion instead of being incorrectly looked up as REST catalog views. Existing tables still take precedence, and ordinary REST views continue to use the current fallback path. ## Validation - `cargo test -p paimon-datafusion --lib sql_context::tests::registered_table_function_skips_view_lookup_during_relation_preload -- --exact --nocapture` - `cargo test -p paimon-datafusion --lib rest_catalog_view` — 26 passed - `cargo check -p paimon-datafusion` - `cargo clippy -p paimon-datafusion --lib -- -D warnings` - `cargo fmt --all -- --check` The full `paimon-datafusion` library test run with `fulltext` reached 274 passing tests. Seven existing scan tests could not load their expected table fixtures 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]
