shyjsarah opened a new pull request, #272:
URL: https://github.com/apache/paimon-rust/pull/272
<!--
Thank you very much for contributing to Paimon Rust - we are happy that you
want to help us improve it. To help the community review your contribution in
the best possible way, please go through the checklist below, which will get
the contribution into a shape in which it can be best reviewed.
## Contribution Checklist
- Make sure that the pull request corresponds to a [GitHub
issue](https://github.com/apache/paimon-rust/issues). Exceptions are made for
typos in documentation or comments, which need no issue.
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `cargo test`
passes.
- Each pull request should address only one issue, not mix up code from
multiple issues.
**(The sections below can be removed for hotfixes or typos)**
-->
### Purpose
Linked issue: N/A
Fix silent error swallowing in DataFusion catalog integration. Previously,
catalog errors were silently converted to "table not found" or empty results,
making debugging extremely
difficult.
### Brief change log
- `schema()`: return provider optimistically without calling
`get_database`, deferring errors to `table()` which has a proper `Result` error
channel
- `schema_names()` / `table_names()`: replace `unwrap_or_default()` with
`match` + `log::error!` so catalog failures are visible in logs
- `table_exist()`: log non-`TableNotExist` errors at error level before
returning `false`
- Add `log = "0.4"` dependency
### Tests
Existing tests pass. The change is behavioral — errors that were silently
swallowed now either propagate (via `table()`) or appear in logs.
### API and Format
No API or storage format changes.
### Documentation
No documentation changes needed.
--
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]
