shyjsarah opened a new pull request, #627: URL: https://github.com/apache/paimon-rust/pull/627
### Purpose Linked issue: close #626 Make DataFusion `SQLContext` use Paimon database semantics instead of delegating database statements to DataFusion catalog/schema behavior. ### Brief change log - Handle `SHOW DATABASES` through the current Paimon catalog and return a sorted `database_name` column. - Handle `CREATE DATABASE`, `DROP DATABASE`, and `USE <database>` through Paimon catalog APIs. - Support current-catalog and `catalog.database` name resolution. - Support `IF NOT EXISTS`, `IF EXISTS`, and `CASCADE`; reject unsupported statement options explicitly. - Keep `CREATE SCHEMA` and `DROP SCHEMA` as compatibility aliases. ### Tests - `cargo test -p paimon-datafusion --test sql_context_tests` (53 passed) - `cargo test -p paimon-datafusion --lib sql_context::tests` (165 passed) - `cargo clippy -p paimon-datafusion --lib --tests -- -D warnings` - `cargo fmt --all -- --check` A full local `cargo test -p paimon-datafusion --lib` completed 315 tests successfully; 7 existing table scan tests require pre-populated `PAIMON_TEST_WAREHOUSE` fixture tables and failed because those fixtures were not present locally. ### API and Format Adds SQL behavior to `SQLContext`. No storage-format changes and no public Rust API signature changes. ### Documentation Updated the SQL DDL documentation to use database terminology and document the supported statements and compatibility aliases. -- 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]
