QuakeWang opened a new pull request, #101:
URL: https://github.com/apache/paimon-rust/pull/101
<!--
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
Fix `FileIO::list_status` path semantics: each returned `FileStatus.path`
now points to the actual listed entry instead of the input directory path.
Also, keep reusable operators in `Storage` to preserve memory backend state
across calls.
### Brief change log
- Fix `list_status` to return real entry paths (`base_path + entry.path()`),
and fetch required metadata via `list_with(...).metakey(...)`.
- Refactor `Storage` to reuse `Operator` instances across calls (including
memory backend).
- Add regression tests for `list_status` on both `fs` and `memory` backends.
### Tests
- `cargo fmt --all -- --check`
- `cargo clippy --all-targets --workspace -- -D warnings`
- `cargo test -p paimon io::file_io::file_action_test`
- `cargo test --all-targets --workspace`
All tests passed locally.
### API and Format
- No public API signature changes.
- No storage format changes.
- Behavior fix only: `list_status` now returns correct entry paths.
### Documentation
No documentation update required.
--
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]
